General

  1. Composite Step Templates

    There are sets of common steps that we very often want to "bookend" all of our deployments with. One concrete example would be: sending out a Manual Intervention to confirm when all servers are confirmed live before stamping a new deployment in NewRelic.

    Right now, everyone has to bake these steps into their own projects by adding the Manual Intervention step followed by the NewRelic Deployment Stamp step. If it were possible to create what I would call "Composite Step Templates" then I could define a reusable step template that was made up of other step templates. That way, instead…

    821 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  30 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Automatically retry steps if they are failed

    Now when a step failed you have to set guided failure on in order to retry the step, it would be handy to have a setting where you say always retry failed steps.

    For example if you are doing continues deployment where a build server triggers a deployment from a build, you have to:
    - login into octopus
    - select the correct project
    - manually intervene and assign it to you
    - retry it

    It would be much better if the retry can be done automatically

    351 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Automatic release creation to multiple channels

    It would be helpful to be able to specify multiple channels for automatic release creation. The way we are using channels, no package is eligible for more than 1 channel. Without this, the development team now needs to remember that for some channels they don't need to go to octopus to create the release and for others they do.

    253 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow new IIS step to just create IIS resources without necessarily deploying a package

    Currently the new IIS step (introduced in 3.4.7) allows you to create Sites, Apps and Virtual directories, but you always have to deploy a package.

    It might be useful for some users to be able to take advantage of the IIS functionalities, without having a deploy a package.

    Source: http://help.octopusdeploy.com/discussions/questions/9702

    231 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Make the Blue/Green Model the Gold Standard of Deployment with Zero Downtime

    In my mind zero-downtime deployment is the gold standard of deployment. Octopus should support this model to the fullest. Given proper tooling (in Octopus) this is very easy to accomplish for customers.

    I think most ASP.NET apps should be deployed in the following way:

    1. Put the app behind a load balancer such as ARR (built-in and free)
    2. For each new deployment create a *fresh* IIS site
    3. Configure the site
    4. Request a configurable set of important URLs to start the site and warmup caches
    5. Validate, that those URLs return 200 and contain a given check string…

    206 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add support for setting Windows Service Recovery options

    Add the ability to set the actions to be taken on service failure. This is accomplished via sc as follows:
    http://technet.microsoft.com/en-us/library/cc742019.aspx or using Powershell set-service.

    At present, we are managing with a custom PowerShell script.

    195 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support deployment of Azure Function projects

    Support deployment of Azure Function projects

    180 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Associate variables with a Release when creating one

    When creating a release, allow variable values to be set that will then flow through to all deployments of the release. See: https://github.com/OctopusDeploy/Issues/issues/1149#issuecomment-52598811

    168 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow cloning of tenants

    It should be possible to clone a tenant including it's current configuration in a similar way to that you can clone whole projects.
    Tenants tend to be similarly configured with only minor changes to each one so it would save time rather than having to configure each one from scratch.

    145 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow creating a Channel Version Rule that applies to all Steps

    In Octopus 3.2 the Channel Version Rules only apply to explicitly selected Package Steps.

    When adding a new Package Step, you need to remember to add that Step to all of the Channels that apply, otherwise when creating a Release, none of the Version Rules will apply to that new Package Step.

    What if you could create a Version Rule that applied to ALL Package Steps as an alternative to being explicit?

    This could be more convenient, and safer-by-default, when people follow a consistent convention for versioning the packages in their Projects.

    134 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Library variables usage from Script Console

    Currently (2.6.x) its not possible to use Octopus variables from the Script Console. It makes sense that Project variables cannot be used from the SC, but variables from Library Sets might be a good idea.

    123 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 →
  12. Add timeout support for individual steps and overall deployment

    We just found an issue where our CI deployments via Octopus had been backed up for more than a day because one of them was hung on an FTP to Azure issue. We found out because a tester tried to run a promotion to Test which didn't complete in a timely manner.

    This highlighted that there is no step timeout available so that we could for example have the step fail if it doesn't complete within X minutes. Similarly, we should be able to fail the overall deployment if the collective steps take longer than Y minutes.

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

    Until we implement this feature, the work around would be to monitor the deployment using the API and cancel it if a timeout has been reached.

    I have written up a script (https://octopus.com/blog/automating-octopus-with-azure-functions) that retrieves all running deployments for a project and cancels it if:
    - it has been running for more that 30 minutes
    - the first step has been running fro more than 20 minutes
    - the first step has not output any logs in 5 minutes

    This can run as a scheduled task. Alternatively you can use the subscriptions feature to kick off a piece of code (eg Azure function) that does this polling, as described in this blog post: https://octopus.com/blog/automating-octopus-with-azure-functions

    — Robert W

  13. Allow a step to fail and not mark the deploy as failed

    For steps like 'post to a slack room' or 'update the build server with a token', I think it is reasonable to provide some sort of toggle to allow the step to fail without failing the entire deploy.

    111 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow Variables to be Version Controlled

    Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.

    I would like to be able to version octopus variables, this would include:
    - Who
    - When
    - When deployed
    - The ability to roll back/forward.

    At the moment we have to source control much of this type…

    110 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Highlight the variable Snapshot difference while updating the release snapshot

    Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done…

    78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add an option to notify members of the responsible team on Manual Intervention Steps

    When adding a manual intervention step (say for approval to deploy to production) It would be nice to have a checkbox on the step configuration that sends an email to all users of the "responsible teams" containing the instructions and a link to the release.

    While we're on the subject, it would also be great to be able to set a Team as an addressee on the the Send Email step template.

    69 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 →
  18. Add "QueuedBy" system variable for obtaining user who has actually queued deployments

    I'm getting persons username when receiving deployment status email from automatically triggered deployment (by Project trigger on machine becomes available event). In the email template i'm using Octopus.Deployment.CreatedBy.Username system variable to display user who has run deployment.
    So in case of auto-triggered deployments I would like to get value "System" instead of some person's username (apparently one's who first has run the deployment manually).

    Ref: http://help.octopusdeploy.com/discussions/problems/52736-octopusdeploymentcreatedbyusername-value-is-not-system-when-deployment-fired-by-project-trigger

    67 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 →
  19. Add Let's Encrypt support to the Certificates Library functionality

    I love the Let's Encrypt integration with the OD server. Setting up SSL for the server is so simple, and I don't even have to worry about renewals as this is taken care of for me.

    Now imagine this same functionality for all of your IIS sites.

    This is how I envision it could work

    - I go to Library > Certificates > Add certificate
    - I'm given the option of importing a cert (i.e. the current functionality), or I can chose to use Let's Encrypt
    - After picking Let's Encrypt, I'm prompted for a bit of info- domain, email…

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Enhanced variable substitution in ARM template deployment

    When using an ARM resource group deployment, Octopus asks for parameters file, which is JSON, and replaces parameter values with matching variables.

    We would like to use the JSON variable substitution syntax mentioned here: https://octopus.com/docs/guides/deploying-asp.net-core-web-applications/json-configuration-variables-feature

    this would help us maintain a working parameters file that can be used outside of Octopus.

    64 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 →
← Previous 1 3 4 5 23 24
  • Don't see your idea?

Feedback and Knowledge Base