General

  1. Support v3 NuGet Feeds

    Currently there are a few feeds that support v3 NuGet feeds. Octopus currently does not support linking directly to the JSON file. Please add votes and feedback on why you would like this supported by the few feeds that currently do.

    Please note that this is not about Octopus updating its NuGet library to support things like SemVer 2.0 which is planned. This is strictly when you add an external feed to retrieve external packages.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Find variable usage across all projects and variable sets

    When working with library variable sets used in many projects with many steps it is cumbersome to figure out where a given variable is used.

    When updating a deployment process, certain tasks become very difficult, such as:
    -Renaming or deleting a variable
    -Checking validity of a newly-updated variable value across all usages

    With a "find all" feature these tasks would be much simpler (plus I'm sure there would be wider-reaching benefits).

    343 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    Happy to announce we’ve added a usage tab to the variable set page in 2019.5.4, where you can view which projects and releases are using a variable set. While this does not cover all suggestions below, we are confident that this goes a long way to solving the problem.

    Finding the usages of individual variables is something that is a lot more complex than it sounds, and we are unlikely to implement. Many variables usages are embedded in strings, or even in files sourced from packages, meaning any results we displayed would be incomplete.

    If you think we’ve misinterpreted this suggestion, please raise a new suggestion with a bit more detail about the use case, and let us know in the comments below.

  3. Automatic release creation to allow packages with variables in IDs

    Currently the automatic release creation feature does not resolve variables when looking if a package is used in a project set for automatic release creation. You can only use package IDs with static names.

    It would be great if you could use variables in the package ID and have them resolved when the package is pushed.

    Source: http://help.octopusdeploy.com/discussions/problems/28069

    217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Viewing variables for a release should evaluate nested variables

    I regularly use nested variables to minimise the number of variable changes I must make between environments. Consider something like this:

    data source=#{Database.Server};initial catalog=#{Database.Name};#{Database.Auth};

    This allows me to just specify simple variables for the DB server, the DB name and the type of auth being used, without having to construct a connectionstring every time (and probably making the odd mistake).

    It would be great if I could see the fully-evaluated variables when i click "Show variables" on a release - or at least have a switch between the raw variables and evaluated variables.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add an option to only create a binding in IIS if it does not already exist

    We would really like to have an option to leave bindings alone in IIS if they already exist.

    I configure a single binding as a templated deployment step. I would like octopus to automatically create the IIS app and bindings in the event the app pool and website doesn't exist - but if it does already exist I'd prefer it not to reconfigure the bindings.

    This is useful when we create website aliases for production environments which don't fit the normal QA and UAT environment setup (but they happen to use the same steps).

    Best would be a checkbox:

    "Overwrite…

    148 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add support for Python scripting.

    It would be great to see Python listed as a script step. Python is heavily utilized in the infrastructure space, AWS, F5, Citrix, VMware and will help to drive full automation further up the stack.

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Skippable Steps by default

    Is there a way to make a step skippable by default?

    I know the request might sound strange, but we're run into a scenario where a step may need to be run in certain scenarios. Obviously the user could skip the step by hand each time, but considering the default is to run each step, we're trying to avoid a scenario where someone doesn't look and just runs the default. This would make it very apparent that the step isn't run (as it will be marked as skipped) and force the user to look into it with more detail.

    Odd…

    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for voting on this. I think that the “channels” feature we added in 3.3 is a solution to this scenario – you could set up channels like “major release (all steps)” and “tiny bugfix (run 1 step)”.

  8. Virtual Dashboard

    https://github.com/OctopusDeploy/Issues/issues/447

    It'd be awesome if clicking on a Project Group in the Projects drop down took you to a dashboard that ONLY listed the projects under that group.

    Better if an admin user can still hide/show projects in those virtual dashboard for everyone

    Even better if each user could configure a custom version of that dashboard for themselves

    132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Compliance with latest SemVer

    Would like that OD is in compliance with the latest version of SemVer, so that the Pre-Release flag, and Build Metadata can be utilized in the release number.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add ability to indicate whether Windows Service should be started on deployment

    In some environments we do not want a Windows Service started after it is deployed. In the current Octopus.Features.WindowsService_BeforePostDeploy.ps1 file the service is always started. It would be great to have a flag that could prevent the service from being started.

    159 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add XmlPoke feature for setting random config values using XPath

    It would be nice to be able to set random values in the config files using an XmlPoke type feature where you could specify XPath expressions that point to values in the config file and then specify values to set them to.

    Here is an example to set the compilation debug to false:

    XPath: configuration/system.web/compilation/@debug
    Value: false

    This would allow setting random values throughout the config file without having to use config transforms.

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Rather than allways taking the "latest" version of a package, can we scope the step to within a particular version range

    When you create a release, Octopus default to picking up the latest version of the available packages.

    We have multiple forks of our packages, and we need to be able to restrict a package step so that it is limited to a particular version range of the package, for example:-

    If we have a major version 1 of a package on a step,

    If we later create a fork and do work on a major version 2,

    We do not want the next octopus release to pick up major version 2 - we want to limit the scope of the…

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow me to choose which environments a project uses / per project environments

    We have multiple projects being deployed to different servers in heterogeneous environments. Some are just test-production, others are dev-test-staging-production. The projects often have completely separate environments.

    It would be beneficial to be able to either choose which environments a project can deploy to, or to be able to set up per-project environments to be able to keep the same names for config transforms. (ex. "Web.Test.cfg" instead of "Web.Test-Product1.cfg")

    Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support semver 2.0 build metadata in the release version.

    In our project we have 2 branches - trunk and patch - both of which produce packages for Octopus and use semantic versioning when creating the Octopus release in the build. I would like to specify a build from the patch branch explicitly so that when packaging off the trunk my release would be 1.24.102948 but when packaging off the patch branch my release would be 1.24.102949+patch. My workaround is to use the pre-release metadata so my patch builds are producing octopus releases 1.24.102949-patch.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. allow the Email Step to flag the email as High Priority

    A flag on the Email template step to send the email as High Priority. We use the Email template step (when any step fails) to notify that the deployment failed and it would be more convenient if we could set the flag for high priority. I could create my own powershell step, but I thought the out of the box email template step could use this feature.

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  16. promote a whole environment

    We have "major deployments". At this time we have to deploy all our applications (~ 70) at once. So it would be nice to have a possibility to deploy all projects from environment-1 to environment-2

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Quick search for Releases no longer available in Octopus v4.0+

    Current configuration (v4.0+) uses dropdown control for Releases list.
    Previous implementation had combo box control and it allowed to do a quick search for large releases lists.

    Would love to have this feature back since currently it is not possible to do a 'contains' search among differently named releases.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Have an option to disable the Guest/Account question on the splash screen as I always want to login with an account.

    Logging in always takes a few clicks with the Guest/Account question. As a dev I never want to see the guest option. Can there be a way of preventing it showing - perhaps via a cookie such as "Remember this choice"?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Paul! You can do this already by disabling the Guest Authentication Provider: octopus.com/docs/administration/authenticat..

    You can do this via the UI in more recent versions of Octopus, or you can always do it through the command-line interface. Details are on the page.

  19. Show Release Notes as a column directly on the Releases page for a product

    When you list the releases for a product you can see the Version and when it was assembled, but not the release notes. We have this connected to the git commit log so we easilly can see what is being deployed. Right now we have to click each item to see this information

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Configure dashboard to allow selection by project group

    Provide an additional option in Configure dashboard to allow selecting project groups instead of just individual projects. This way if an additional project gets added to the group it automatically appears on your dashboard rather than having to look for and add new projects to the filtered list.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base