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. Allow variable version for packages when creating releases

    We have a nuget package which has been named after our tenants.

    We want to deploy the package as a part of our overall pipeline, however when we generate the release it wants a version number for that package, and each package has its own individual version, as some tenants have their package updated more often than others.

    We would like Octopus to resolve the Package Version at deployment time, just like it resolves the Package ID when using a variable binding expression.

    In this case it would be useful if you could specify "*" or "latest" (think docker) so…

    58 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    • Add cmdlet to download artifact

      New-OctopusArtifact allows you to attach an artifact to a release. If you wanted to use that same artifact in another step on the same deployment, you'd need to use the API.

      It might not be such a bad idea to have a `Get-OctopusArtifact` cmdlet that returns info about that artifact, as well as a `Download()` method the download the full file from a Tentacle.

      18 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
      • Moved recetly deleted projects into a "trash" location so can easily restore them

        I have accidentally deleted projects multiple times now.
        When I am in a rush and want to manually recreate a release I have to delete it - which has a very similar sequence of actions required to delete the project! :(
        The only way to get the project back is to restore the database. It would be nice if you could just hide the project from the GUI and keep it into a trash can somewhere which could retain it for a limited perioud (e.g. a month).

        36 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
        • Octopus.Migrator shoud not use meaningless "IDs"

          Since the content type and name is obviously a unique key (particularly when exporting to files), Migrator should use the name (prefixed by the type name) as the key when linking from other resources, rather than a phony ID that changes when you import.

          That is, rather than a Team having MemberUserIds = [ "Users-1" ] it should have MemberUsers = [ "Users-BobCratchet" ] which is both more comprehensible, and unlikely to change in a simple import and re-export.

          We do modifications to our Octopus by exporting from production, importing on a dev system, altering, and re-exporting. However, the IDs…

          3 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
          • Create jobs for recurring tasks. Use permissions to control task jobs by environment.

            Create task jobs for recurring tasks. Use permissions to control task jobs by environment, project, node.

            The QA Team could be assigned permissions on a task job to run an iisreset on all servers in the QA environment or particular projects in the environment. Dev Leads could restart Windows services on individual nodes in Dev. Right now a user has to be an Octopus admin to run a custom shell script but we don't want the Dev teams to be able to affect production. I'd rather just create a task job so Dev or QA does not mistakenly run the…

            11 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
            • Timer for manual intervention steps

              We use manual interventions in several projects. Rarely (but it happens anyway) team press deploy button and go to drink a cup of tea, so when manual intervention interrupts deployment there is nobody who can agree or cancel deployment resumption.

              This issue could be easily solved if maual intervention step had timeout and fail/succeed after timeout came out.

              9 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
              • Release variable for channel + environment

                Currently there are release variables for

                #{Octopus.Release.PreviousForEnvironment.Number}
                #{Octopus.Release.CurrentForEnvironment.Number}

                But I would like to see something along the lines of

                #{Octopus.Release.PreviousForChannelEnvironment.Number}
                #{Octopus.Release.CurrentForChannelEnvironment.Number}

                We have deployments spanning multiple channels, environments, and tenants. At the end of the deployment process, we send a release e-mail that explains what version the instance was upgraded from and to. However, the current variables only lead to confusion as without the channel taken in to consideration, the messages end up saying things like

                "Upgraded from 6.4.X.X to 6.3.X.X.X", which is backwards because the '6.3' channel just happened to be the last release deployed in that environment. I…

                25 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                • 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.

                  236 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    13 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                  • Make variables groupable/collapsable

                    In the project I'm currently working in; we have 6+ environments and many variables are unique to these environments.

                    To get a better overview of all the variables I suggest that you add the possibility to collapse or group the variables by name.

                    13 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      2 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
                    • Stop or Fail deployment if some tokens cannot be evaluated

                      It might sometimes occur that a replacement token is not (yet) defined. OctopusDeploy uses verbose logging to add this to the deployment logs ...

                      Would it be possible to make this configurable, so I can decide that, in this case, I want my deployment to stop or fail, so I don't end up with partially correct configuration files ...

                      If this should already exist, please point me in the right direction ...

                      Thank you in advance!

                      10 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                      • Sales Force Integration with Octopus Deploy

                        1. Enable File System deployments - Deployments to be carried from a file share
                        2.Possibility to automate the sales force Continuous Delivery feature using Octopus Deploy.

                        80 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
                        • Port Octopus to .NET Core

                          Moving Octopus Server/Tentacle/Calamari to .NET Core would extend the reach of Octopus Server to other platforms.

                          - List item 1
                          - List item 2

                          196 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            5 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

                            We have put this task on hold as the .NET Core libraries do not yet have all the bits we need.

                            We have however ported the following to .NET Core:
                            - Octostache
                            - Halibut
                            - Octo.exe
                            - Octopus.Client
                            - Most of Calamari

                            This means these tools can be used on Linux.

                            We have also built https://www.icanhasdot.net/

                            We may pick this item up in the future, one the platform matures.

                          • Run Tentacle on Linux

                            We are investigating the ability for Tentacle to run on Linux and want to know in which situations that would provide an advantage over using SSH. Please leave your comments below.

                            8 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              3 comments  ·  Flag idea as inappropriate…  ·  Admin →
                            • Require two users to authorise a manual intervention step

                              It would be good if you could (optionally) require two users to authorise a manual intervention step.

                              10 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                3 comments  ·  Flag idea as inappropriate…  ·  Admin →
                              • 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.

                                115 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                • ServiceNow ITSM Integration

                                  The ability to integrate into ITSM products like ServiceNow for change request time frame verification when a deploy is triggered.

                                  34 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Filter Environments Shown on Project Overview Page

                                    When I navigate from the dashboard to the Project Overview page, the page should only show the environments that I selected on the Configure Dashboard screen. Also, it would be helpful to filter the list of environments by channel or lifecycle.

                                    11 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      3 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Allow cloning Library Variable Sets

                                      Allow cloning of library variable sets so it becomes easier to create a new variable set for a new environment.

                                      48 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        8 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Support variable prompting for offline deployments

                                        The current offline deployment comes with the assumption that the target environment is known. We have dev, test and staging environments that we control. Unfortunately we don't control production due to security constraints. We also have a lack of visibility into that environment such that we don't know the variables for production (like database server names, usernames and passwords).

                                        It would be great if a variable could be marked as "Prompt" such that the offline deployment execution can ask the user on the console for the variable values for the keys marked as Prompt.

                                        17 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Define dependencies on PS modules/scripts hosted on PowershellGallery.com (or similar source) in script modules and templates.

                                          Allow defined dependencies on powershell modules or scripts (and versions) from a nuget compatible source such as PowershellGallery.com. Allow these dependency definitions anywhere powershell is used in Octopus. Tentacle should install the scripts/modules into the Powershell Session prior to performing any release steps.

                                          This would allow for more complex powershell modules to be made available for Octopus to use, as well as a means for keeping the PS code up to date outside of Octopus.

                                          11 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
                                          • Don't see your idea?

                                          Feedback and Knowledge Base