Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    364 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  40 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    211 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    119 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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.

    99 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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 (a smoke test)
    6. If all…
    82 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Support deployment of Azure Function projects

    80 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    79 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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…

    67 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  7 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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.

    66 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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

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

    61 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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.

    60 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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.

    55 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
    In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
    This is not possible now, the only solution now is to cancel all the existing tasks.

    53 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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…

    37 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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.

    37 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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 address, verification process…
    36 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Ability to import project variables from a JSON file under the Project page.

    34 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. It would be very nice to be able to decide the order of a rolling deployment. Perhaps by setting a sort index on each machine in an environment. Today it seems a rolling deployment is always performed in the same order, but it is unclear what decides that order.

    31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Since 3.4 the Project Overview dashboard is now grouping and sorting by Channel name, with the default channel at the top. Previously, the recently created releases were at the top, allowing for quick promotion.

    We have many channels, which are numbered, and with the current sorting, the newest ones appear at the bottom, and out of order (e.g. default, 100, 101, 75,etc.).

    It would be nice to add the ability to re-order the channels (on the channels page) similar to how you can re-order steps and environments.

    28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 25 26
  • Don't see your idea?