General

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow steps to be 'disabled' or 'inactive'

    At the moment when editing a step, you can specify which environments it is to be run in. Selecting no environments means that the step will run in all environments. There's no way to specify that a step should run in no environments.

    If I have a problematic step and I'd like to take it out of use temporarily while I work on it, I'd like to disable it somehow, maybe with a checkbox on the process page.

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

    648 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Azure PaaS Server

    Run the Octopus server completely on top of PaaS offerings. You could use a Web App site extension to install/run the server (an HttpPlatformHandler might be an easy way to utilize the existing windows service executable), an Azure SQL database for the backend, and a blob storage account could be your NuGet package repository.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Cloning of steps

    It would be nice if I could clone steps inside processes. For example if I want to deploy two nuget packages, I need to create one step to deploy a nuget and again create another step to deploy a nuget, instead of just cloning it. It's a waste of time!

    279 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Major and Minor version numbers as individual variables available for use

    We deploy to a sub app on the site for our Web services with the major/minor version number in the URL to allow for easy side by side deployments. We don't deploy every version to a new URL because of the volume of builds we get for dev/testing etc. and we like to give a friend URL out to 3rd parties that use them.

    e.g. https://MyWebService.com/v1.2/MyService.svc

    currently we have custom powershell to update the IIS location in predeploy, we hard set it to something like "MyIIS.Site/v1.2", would be good if we could get the specific number using variables and use…

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Ability to reorder step template parameters

    It would be nice to have the option to reorder step template parameters just like one can reorder the environments.

    Right now step template parameters are displayed in the same order they have been created. If one does not pay attention to the order at that time then I can only export the json string, change the parameter order, delete the step template and reimport my modified version.

    Also if a step template is modified at a later time and parameters are added or removed, then the order of the parameters might be now incorrect. Imagine that I want to…

    131 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Lock "production" releases from retention policy

    Via @DotNetWise (https://github.com/OctopusDeploy/Issues/issues/1157)

    Retention policy helps you to cleanup the mess, but it could possible destroy your live releases.

    You DO want to apply retention policy on live servers, but not for those releases you know there are being used / live etc.

    Hence, add the ability to lock a release, so it won't be deleted by the retention policies.
    Later on, I could unlock it and it will go away on when the next retention policy is being applied.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    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)”.

  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Audit trail and report for permissions\role changes of users

    Recently we have been audited and one of the questions asked of me was to provide a control for how permissions are managed. At the same time provide me with evidence that you periodically review permission changes using a system generated report. This would be very simple to implement using the same audit structure currently used for the deploy process and it would make auditors happy.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add "Substitute variables in files" feature in "Run a Helm update" step

    In "Run a Helm update" step we need: Enabled Features -> Substitute variables in files

    Why?
    For example we need to create configMap for our helm-chart. App config locate in this chart, so we need replase all #{values} by values from project scope

    Step helm_install:
    1. download chart
    2. Substitute variables in files (choose location)
    3. in custom script (deployment step) create configMap for our pods

    If this feature doesn't exist: we need another step where we download app config and substitute variables and use this file to create configMap

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base