General

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. Version control configuration

    This was originally raised at https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6186352-version-control-of-deployment-scripts and closed as completed with a solution of scripting the import/export tool.

    Raising as a new suggestion as this has come up as few times in support calls and some people have suggested on the original thread that the import/export tool doesn't meet their needs. (Didn't want to reopen the original thread as some people are happy with the provided solution in that thread.)

    "In the Continuous Delivery book, Jez wrote that your deployment scripts should be in source control. After creating some pretty elaborate powershell scripts for Octopus, I have to agree. Losing…

    473 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      17 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
    • Integration with Microsoft Teams

      Microsoft Teams already has a pretty great list of connectors, but one big one is missing... Octopus Deploy!

      I would like to be able to receive messages in a channel when a deployment is complete, or certain events happen.

      132 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        6 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
      • Allow octo.exe to generate results in machine-readable formats (i.e. JSON/XML)

        octo.exe is a great tool that wraps much of the Octopus Deploy API. It would be great if we could specify a parameter --output-format=json or --output-format=xml to have octo.exe generate its results in a machine-readable format for further scripting (e.g. in an environment where I have an older version of Powershell without access to modules such as Octoposh).

        3 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          started  ·  0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
        • 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…

          706 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            13 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
          • 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
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
            • Enable triggering deploy for entire group

              When you got a lot of microservices inside a group, one click to start deployment for all of them in their defaults lifecycle

              3 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
              • Create a Widget for Microsoft Visual Studio Team Services

                To create the ultimate overview on your Visual Studio Team Services (VSTS) Dashboard it would be great if Octopus offers a widget where you can see the Octopus dashboard overview for your project.

                More information on VSTS Dashboard widgets: https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-dashboard-widget

                18 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  started  ·  1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
                • Built-in AWS support (like for Azure)

                  Improve Amazon Web Services integration by adding built in support for AWS.

                  Example: give your AWS credentials to Octopus and him will create automatically an instance with a Octopus tentacle installed on it.

                  38 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

                    We have started work on some basic AWS support that will probably be released in Q1. This first installment will be initially limited to exposing an AWS account type and a cloud formation step. From this starting point we intend to extend our 1st class support to other AWS services throughout the year.

                  • Octopus step templates linked with github

                    We currently are writing many powershell scripts to work with octopus deploy as part of our deployment and then having to keep a copy in our github repo to be used by the devteam. I'd like a way for octopus to have access to the repository and notice there are changes and allow for a manual update, as it currently works.

                    17 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

                      We plan on providing support for GitHub feeds so that “packages” can be sourced directly from GitHub, using the tags to determine versions.

                      With this approach so long as your script is in GitHub, and you can tag your commits, Octopus will be able to pull down the repository source code and use that script in the deployment as it does today with existing script steps (https://octopus.com/docs/deploying-applications/custom-scripts/standalone-scripts#Standalonescripts-Choosingwheretosourcethescript)

                    • 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
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                      • Recurring Scheduled Deployments

                        It would be great to have an ability to create a recurring scheduled deployment, such as each Monday at 9:30 pm promote from QA to Staging

                        Source: https://octopusdeploy.uservoice.com/admin/tickets/1640

                        464 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          25 comments  ·  Flag idea as inappropriate…  ·  Admin →

                          We have started this feature https://github.com/OctopusDeploy/Issues/issues/3633

                          Until this feature is implemented, there are a few achieve this as other commentators have mentioned.

                          We have a code sample (https://octopus.com/docs/guides/coordinating-multiple-projects/project-coordination-code-samples#ProjectCoordinationCodeSamples-Promotingagroupofprojects) that promotes releases from one environment to another. This can be used as a starting point. In the same document is a code sample that requeues the current task to run every day.

                          To actually execute the script, a Windows scheduled task, or and Azure function (https://octopus.com/blog/automating-octopus-with-azure-functions) can be used.

                        • Inheritable Templates

                          There should be the possibility to create project templates which can be chossen when creating a new project. This should then not only copy everything, but keep the reference to the template. So when something is changed in the template, all projects based on this template should be updated as well.

                          Steps coming from a template should not be editable in a subproject, but there should be the possibility to disable a specific step in a specific project.
                          Also there should be the possibility to add other steps between "template steps" to customize the process.

                          Teamcity has a simillar model.

                          188 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            6 comments  ·  Flag idea as inappropriate…  ·  Admin →

                            the feature Composite Step Templates has started which should meet most of these requirements. The underlying templates will still be linked so that they can be updated as per normal step templates.

                          • 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…

                            21 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                            • 'Dry Run' Deployment

                              Sometimes deployments are bad due to bad configuration variables that are un-testable before releasing to production.
                              Having the ability to 'dry run' a deployment and see all the task outputs with specific highlighting for variables and evaluated variables would allow the identification of changes that need to be made before actually deploying to an environment.

                              588 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                20 comments  ·  Flag idea as inappropriate…  ·  Admin →
                              • 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.

                                6 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                • 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…

                                  80 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                  • PowerShell desired state configuration

                                    Octopus is a deployment orchestration/application release automation tool. Many companies can benefit from configuration management tools like Puppet/Chef, but for various reasons are unable to use them. On the Windows platform, PowerShell's Desired State Configuration support is designed as an alternative to Puppet/Chef, and makes it easy to automate tasks like configuring Windows features and checking for drift.

                                    However there are limits to using PowerShell DSC for our customers - they may not always be on the same AD domain, there may be security issues, there's no auditing, and no nice central way to manage scripts for the team.

                                    Octopus…

                                    247 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      11 comments  ·  Flag idea as inappropriate…  ·  Admin →

                                      Thanks everyone who provided feedback on this ticket. We published a blog post yesterday showing how to do PowerShell DSC with Octopus – everything from deploying DSC scripts, detecting drift, getting email notifications when drift occurs, and automatically fixing the drift:

                                      https://octopus.com/blog/octopus-and-powershell-dsc

                                      With that in mind, I think many of the comments on this suggestion are “done”. But there might be some areas of DSC support that we still don’t do. I’d really appreciate if you could read the post, and let us know of any scenarios we’ve missed. If it looks like we’ve done nearly everything, I might close this UserVoice suggestion and we can open new, more targeted suggestions for any gaps.

                                    • Don't see your idea?

                                    Feedback and Knowledge Base