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. Deployment Pipeline as Code

    I would like to see the "pipeline as code approach" applied to projects. The main idea is to be possible to define the process of a project using a yml file in a source code repository or package.

    37 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  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    • Display Deployments Requiring Manual Intervention for a Release

      When viewing details for a particular release, we used to be able to see any active deployments that are currently awaiting manual intervention. It seems this is no longer visible in Octopus 4.0. In order to view this, we need to go back to a project's "Overview" to see any deployments that have pending intervention steps to approve. This complicates the workflow.

      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…)
        2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

        Nithin are you talking about in the release page? If so then the deployment status should already be visible, including if it's paused for manual intervention (icon looks like an eye). Could you log a ticket through supportoctopus.com along with screenshots so that we can investigate?

      • Make Azure steps runable from Tentacles.

        The building azure steps only support running on the Octopus Server.
        Please make it so we can run this from the Tentacles.

        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…)
          0 comments  ·  Deployment features  ·  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

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

          • Install Octopus Server on Linux

            I'm in a Linux/Mac shop where chef server is the next best thing. If only I could install the Octopus server on Ubuntu the world would be perfect.

            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…)
              0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
            • Support task on the tentacles

              It could be great to have a place where we can use the tentacles to do some tasks without creating a release.
              For example, in my release process I have the backup files and backup DB steps. I would like to be able to launch it without creating a release.
              I see it as a new tab "tasks" where you can configure some task as you do for the process and it will appear as a button on the different environment where this task is available.

              2 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 →
              • Show date the deploy was successfully completed, not started

                Currently the Dashboard shows when a deploy was initiated but it turns out what most of us want to know is when the deploy completed.

                Suggestions:
                * Add a Octo variable so we can choose whether to show initiated or completed date on dashboard
                * Add a Step type that sets the date shown

                Scenario:
                * Multi-step deploy including a manual approval step
                * A developer queues a deployment late Tuesday evening.
                * The deployer has gone home and returns the next morning to approve the deploy.
                => The Dashboard will show Tuesday evening and confusion ensues when the manager…

                5 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  ·  Flag idea as inappropriate…  ·  Admin →
                • Ability to do swing site deployment between staging and production role

                  We can deploy a release to staging and then promote it to production, it would be great if as part of the promote, we could swing the existing production deployment to staging and then promote the new release to production and also give an option to rollback to previous release.

                  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…)
                    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

                    This is a really interesting suggestion and topic. What I’m not sure about is exactly what Octopus would need to do.

                    Normally for these kinds of things, you deploy the site, then change the load balancer to send requests to the new servers (the swing).

                    What exactly does Octopus need to do? Should we automatically migrate the machines in the environment that we deployed to between the staging and production environments, and move the deployment to production too (or, should we just rename the staging and production environments?)

                  • Integrate smoke tests for post deployment

                    While we can run smoke tests by using the PostDeploy.ps1, such as running nunit.exe or something similar (frisby.js, etc), it would be great to have a way to integrate back into the dashboard (through the rest api?).

                    Related links:
                    http://help.octopusdeploy.com/discussions/questions/214-running-smoke-tests-after-deploy
                    http://help.octopusdeploy.com/discussions/problems/53646

                    http://jimblogdog.blogspot.co.uk/2012/08/walk-thru-using-wolfpack-to.html

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

                      Thanks for the suggestion and for voting everyone. I’d like to get feedback on where we should go with this.

                      There are a few things in Octopus that already help with this – first, it’s possible to package your NUnit tests and run them as part of a package test (we do this ourselves), or to write a PowerShell step that pings your website to see if it is online. So the actual process of performing the tests is pretty easy. Do we need to write more blog posts/documentation to show how it can be done?

                      The next part is viewing the test results – in Octopus 2.0 you can “attach” files to a deployment via PowerShell which are then uploaded and available on the deployment page.

                      Viewing NUnit results XML isn’t that nice though, so I guess it would be nice to be able to render those NUnit test…

                    • Don't see your idea?

                    Feedback and Knowledge Base