General

← Feedback & Support for Octopus Deploy

I suggest you...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Release Manager

    Often times with our release we are deploying multiple configurations. With the way octopus stands now you would have to manually go and deploy each project. What we did was created our own tool that uses the API that allows us to deploy multiple projects at once to a particular environment. Something like this might be nice to build into Octopus Deploy itself.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  2. Allow "Configure Features" in "Run Script" steps

    I want to be able to say, transform a json file, and then run a script.

    Right now the only way to do that is by putting your script into a nuget package, naming it "publish.ps1", using the "Deploy a package" step and targetting it somewhere, then enabling configure features.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  3. Allow Azure powershell steps to run on servers other than the OD server

    The Azure powershell steps run on the Octopus server, which is good for ease of getting up and running and small projects, however it is not great when you've got a lot of steps and a lot of projects. This is especially painful when you've got lots of steps that take time. If a cloud service takes 3 minutes to deploy, and you've got 6 to deploy, that blocks the server for at least 18 minutes.

    This would probably be even more useful if implemented in conjunction with https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6316906-support-run-on-any-tentacle-model-for-deployment.

    I know that some people would prefer still to keep…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  4. Allow updating of existing Step Templates via the Import feature

    The ability to import step templates from other locations (e.g. Octopus Library) is awesome, but if someone updates the step template the import process can not be used to update the copy I have in my Octopus server. I'm forced to delete the step template and re-import it. Obviously if I have N projects that rely on the step template I'm now stuck because I can't delete it when projects are using it.

    Since I can technically update the powershell script and change parameters and so on inside of Octopus Deploy UI itself, importing of existing step templates should just…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  5. Previous deploy variable for environment

    I would love to have a variable available that is similar to Octopus.Release.Previous.Number but instead list the previous release number for the specified environment not the project.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  6. Support "run on any tentacle" model for deployments

    We use tentacles primarily as machines that deploy code to Azure, thus they act more like "Deployment Agents" than "Deployment Targets". As a result, it would be nice to be able to configure a project/step/etc. to run on the first available tentacle in a pool (defined by environment/role/whatever).

    Right now, if I were to have a role "azure-deployer", and I had multiple tentacles in that role, my steps would run on ALL tentacles in that role. Instead, I'd like to be able to have it run on the first available tentacle. Of course, an alternate solution (that we are using…

    92 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base

(thinking…)