General

  1. Upload artifacts via UI

    Please add support for uploading artifacts also via the user interface.

    Uploading reports/approval documents or other files to a release is currently not possible via an upload button. We have to do a workaround using a script that uploads files from a specific folder or using the API to attach files to a release.

    Especially during Octopus approval steps people need to upload documents.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Deployment Email Preferences by User

    Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add the ability to disable specific environments to all but system administrators

    When we're doing mass maintenance to an entire environment, it would be useful to be able to disable non-admins from doing things to that environment, and display a banner (e.g."Deployments to production are disabled while servers are being re-racked") without stopping activity in other environments.

    Looking for something much like the system-wide maintenance mode, except environment specific.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow setting Build Information WorkItems

    Currently Push Build Information API and command line ignores values set on WorkItems field, only to auto populate with values once one of the Integration extension is enabled.

    Please allow Push Build Information API and Command line to
    - Set WorkItems with values set on request
    - Do not override values even if Issue Tracker extension is enabled

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Please support deployment to Azure Cloud Sevice (Extended Support) targets

    Microsoft opened up a preview for ARM base Azure Cloud Service, which is probably hinting on them moving away from a Classic cloud service deployment model:
    https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/overview
    Please add support for this type of targets.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add tenant tag support to runbook scheduling

    Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add parameters to Runbooks

    This would be like runbook specific variables, but they are defined on the runbook and don't make sense to be in the published snapshot. They would generally be prompted values, but that shouldn't be required. They would be "snapshotted" when you run the runbook. When you are scheduling runbooks with a trigger, you should be able to provide values to use when the runbook is triggered.

    For an example use of these, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Create deployment step skipped or failed as subscription-eligible events

    We would like to get notices when any deployment process either skips a step (for instance because there are no available targets) or when a step fails.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Operations Dashboard

    I use Runbooks to check things in my Kubernetes cluster. I can run these on a trigger, but I have no way to surface them if there is a problem.

    It would be really useful if Octopus Deploy had a dashboard that had configurable "Widgets" (or some such thing). You could have several different kinds of "Widgets", but the simplest would be one that has two states, "Needs Attention" or "Fine" (along with some text for context).

    So I could define one of these Widgets, lets call it Container Base Image Status (a real example for me). In that widget…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add Support for More Runbook Triggers

    The only Runbook trigger right now is a scheduled trigger.

    I would like to suggest two more trigger types:


    Helm Chart Package Trigger:

    When a new Helm Chart version of a package is published, then the trigger would fire. (Allowing the calling of a Runbook.)


    Version Control Trigger:

    If Octopus Deploy added a VCS trigger, then it would allow us to use GitOps.

    Both of these allow Operations to enable control from check in / merge point in source control.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Control when Tentacle retention policy step will be executed during deployment

    Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
    This behavior is by design and can't be configured.

    This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.

    As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.

    I would like to have an option to control when the retention…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support for NodeJS as scripts

    Right now supported is Powershell, Bash, C#, F# and Python

    Would be nice to be able to write nodejs scripts as well

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow for metadata on internal packages

    We want to be able to add custom values like commit id for example on packages

    This would help knowing which commit id the package comes from, at the moment we are adding commit id in our release notes, but that ties to the release and not necessarily to the package

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. OctopusBypassDeploymentMutex for Script console

    Parallel execution should be enabled or can be switch on the fly in script console. Via a variable, similar to OctopusBypassDeploymentMutex

    With the scenario that there is a process running (read: stuck/looping) in the target and executing a kill command via the script console will get you “waiting for script to finish in task…” so it is currently not the workaround.

    Ref case:
    https://help.octopus.com/t/force-stop-a-step-execution/26682/3

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support for .env files with Structured Variables

    We are currently using React, Gatsby and Parcel which all use .env files for their environment variables

    https://www.npmjs.com/package/dotenv

    Currently .env files are not being recognized, they are assuming they are yaml files, which they are not, they are read similar to java properties as key values

    Right now we have to use variable substitution, but would like to use structured so we don't need to add #{} tags in our code

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Download package option to only keep latest in cache

    There are currently 2 package download options when deploying a release: using the package from the cache and always re-downloading. Both of these are useful, but each has one big downside that I think this feature would correct.

    When using the package cache, Octopus will never pick up changes that were made to the same version of the package. If forcing a re-download, the package cache can quickly fill up, especially with multiple development teams (and yes, we have retention policies configured -- our packages are unfortunately quite large).

    A new option that will just always re-download and keep a…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Subscriptions - Multiple Headers

    It would be great to add multiple headers in octopus subscription payload requests. Atm, it looks to be limited to just one.

    Thanks to this, it would be possible to better control the logic through the application that rewrites/parse the payload and send to a specific webhook

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. add a changelog link to the "New Release" notification

    Currently the "New Release" notification pop-up only contains the new release version number and a download link.

    It would be infinitely more helpful if there were also a link to the changelog page.
    The link cloud be generated from the current version of the octopus server along with the latest release version to show the user the changes that will be included in this new release of Octopus.

    Thanks!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add First Class Support for Blue Green Deployments

    For a product that is all about deployments, not having first class support for Blue Green deployments is.... odd.

    Not a lot is needed. In fact you can't put in too much or it will be too opinionated.

    Basically, all that is needed is something similar to your "tenant" system with a blue and a green line. But also show on the line which one is currently in use.

    The "in use" flag will need a bit of effort as it can be a percentage or a list of users or both. But that is not too difficult to show.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 69 70
  • Don't see your idea?

Feedback and Knowledge Base