Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Under our git process, we utilise feature branches quite frequently. However, this can result in some messiness in Octopus where feature branch releases are mixed up with mainline/master releases. It would be great if a release could be marked as feature/branch release of it was a mainline release and then filter on those release types in the project pages of Octopus. This could be similar to nuget's pre release tag.

    27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Make it possible to put machines into a VPN connection, and have Octopus manage the closing/opening of the connection so that concurrent deployments don't result in closed or hanging connections.

    27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. In very rare cases, some variables need to be updatable and apply to previous releases without having to 'update all variables'.

    A specific example: A server needs to move IP address, and the previous one decommissioned. In all releases it needs to know the IP address is different, but also a variable has changed and only relates to the new code, ad a new one added also relating to later releases. 'Updating all' variables would not work for the release.

    If there was a special global variable area either for projects or like a set where you can change it…

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. As of Octopus 2018.2.3, I'm experiencing a limitation for defining variables per tenant and environment.

    The current ability to define variable templates per project is nice (so we can change the value per environment as the project is deployed to those environments). However, it would be nice to have the ability to define a common variable template that is shared across all projects in the deployment per tenant, but can change per environment.

    I understand this can easily be done via variable sets, but it would be nice to be able to define everything in one place--not simply dividing configured…

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Currently the only way to auto-create a release is to use the built-in nuget package manager in Octopus Deploy. Now with Microsoft VSTS having the ability to have a nuget package manager and with hosted builds, it would help to have external packages to be able to do this. This would help for those who have octopus servers that are not accessible outside of their companies network, but want to use Microsofts hosted build controllers.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. It would be nice if we could track the usage of project or global variables . They can be anywhere and there is nothing worst than having deployment time errors. Having references of the variables would allow variable renaming and safe deletion.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Projects  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. On face value the (new-ish) Lifecycle and Release Blocking features of Octopus Deploy are very exciting, however there is a slight bugbear that makes them impractical for my workplace.

    We use continuous integration practices and as a result, all commits to shared source control repositories are automatically built and (if that build is successful) an automatic release is created / deployed to our development environment. Once the developers are happy with that release (in the development environment) it is then manually promoted to the staging environment for user access testing, after which it can be manually promoted to production.

    The…

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Just like there are variables such as

    .package.nugetpackageID
    .package.nugetpackageversion

    It'll be good to have an Octopus variable that holds the value of the package's release notes metadata.

    There are scenarios where it is useful to add data at build time to the package's release notes, and by having an Octopus variable olding this data, it'll be pretty ease to use that info on other Powershell steps later on the deployment.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. It would be great if we could add a feature to a step (such as the existing Custom Install Directory) from the script modules or step templates. This is not adding a new step, but adding a feature to an existing step. So if I had a script module that I wanted to run as a post deploy on a bunch of steps, I could add it as a feature to those steps. This should also be allowed to happen within created Step Templates, allow a 'nesting' of scripts so step templates could have their own pre- and post- deploy…

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Currently the only way to fake this functionality is:

    AND - #{if var1}#{if var2}true{/if}{/if}
    OR - #{if var1}true{/if}#{if var2}true{/if

    It'll be handy if we could simply have && and || for this, especially since "Run a step on a variable condition" was recently added.

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Currently machine policies are only able to be applied at the machine level. The idea is to set the policies at the environment level so they are applied to all machines within that environment. That would make it easier to manage groups of machines at a time, and would automatically apply policies to newly added machines. This could be helpful in auto-scaling scenarios.

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Support Windows Server 2016 Nano.

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. I'd like to capture some additional fields along side every release.

    For example, every release of my project, should have a corresponding:

    • Team City Build Number
    • Team City Build Type Id
    • Team City Build Id

    At the time of creating a release in Octopus, if done through the octopus UI - these values would be prompted for.

    If done through Octo.exe then the create release command should have the ability to set these release specific property values.

    The reason this is useful is because:

    1. The Octopus Release number no longer has to match the Team City build number in order…
    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Octopus Subscriptions should be extended to include support for running scripts (PowerShell, C# etc) in response to events. That, or allow the community to write their own extensions for Subscriptions (similar to how auth extensions were implemented).

    This would save us from having to setup an external webhook for Octopus to communicate with / cut out the middle man.

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. When a role is not actively being used by a tentacle, it doesn't show up on the role's field autocomplete anymore. The role remains on the deployment processes' steps though. Just because the role is not being used at the moment, doesn't necessarily mean that it wont be used anymore:

    The user just deleted a tentacle with a long role name that is being used on several deployment processes' steps. Couple of min later the user provisions another machine that is supposed to use the same role. This role wont show up on the autocomplete anymore, giving the user the…

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. I use a SQL Project in Visual Studio using SQL Data Tools, it would be nice to be able to deploy to SQL using the DACPAC file it creates, as it can update the database using that file

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. When adding a binding to IIS in Octopus, you can only use seperate variable. Every binding needs a new variable. Some of our deployments have over 50 bindings. We create each binding separate. If we use a variable list only the last item of the list end up in de IIS binding. It would help us a lot if we could ad three generic bindings (Test, Acceptation, Production), en in the bindings use a variable list, containing all the IIS bindings.

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. The ability to hot-link to publicly accessible widgets/icons that show the last Octopus deploy status for a particular project and it's environment. Very similar to how build tools do it (like TC Server, Jenkins, VSTS and Travis CI). See an example here: https://docs.travis-ci.com/user/status-images/

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Please add search functionality to the audit log. The filtering helps but trying to find changes to a variable library for example is nearly impossible.

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?