522 results found

1. Add status filter to dashboard

   When a deployment has failed, it shows on a tenanted dashboard as the latest release, when I'm wanting to know which version was last deployed/currently active (our deployments rollback if unsuccessful), but right now there's no way on showing only success deployments.

   It would be a great feature for this to be one of the Advanced Filters options.

   Also, maybe as a side and could be a bug, that latest release number, even if failed, actually shows up as the current released version when doing a multi deployment i.e. using the Deploy To window

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →

2. Support sharing of variable sets and script modules across spaces

   https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4

   We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.

   We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in the variable set then the apps have the updated whitelist on the next deploy.

   This doesn’t work if teams are in different spaces. I would effectively have to manage several whitelist variable sets across every space which kind of defeats the point. The reason for needing to move to different spaces for each team is that accounts (e.g. Azure Service Principles) cannot be restricted except across spaces and we want to de risk the possibility of one team using another teams account

   https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4

   We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.

   We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →

3. Grouping variables in Octopus UI

   As a project leader I should be able to group variables on Octopus UI. This can be just logical separation.

   This solve the problem with linked variables and help mange them.

   For example It could collapse elements that are in structure - for example: db.username and db.password can be collapse as elements of root db or by labeling variables and then can be filtered by using specific label, for example - db.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →

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

   14 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Deployments  ·  Delete…  ·  Admin →

5. Built-in Azure App Service/Function Restart

   I find that deployments to Azure Functions and standard app services will occasionally fail due to files being locked. This usually requires stopping the app service, re-running the deployment, and then restarting the function or app.

   This can be scripted with Powershell, but since this is such a common scenario, I’d love a checkbox built into the Azure App Service step that provides this ability. Something like “Stop App Service prior to deployment and restart after deployment”.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Deployments  ·  Delete…  ·  Admin →

6. Add Deployments link to Worker View

   Add Deployments link to Worker View like what exists for deployment targets

   Deployment target link path example: /app#/Spaces-1/infrastructure/machines/Machines-xxxx/deployments

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →

7. when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run

   when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.

   idk what you call this icon with the orange square and white lightning bolt

   but when the lifecycle is in this state, the save button really means, “go ahead and run”.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

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

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →

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

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Deployments  ·  Delete…  ·  Admin →

10. Dashboard should be better at visualizing multiple tenants

    Currently the home dashboard displays tenants as a small grey-on-grey count of up-to-date tenants vs total tenants. It would be nice to see a coloured pie chart or similar visualization instead, to make it more obvious when one tenant in an environment is still running an old version or has had a failed deployment.
    It can be easy to miss failed deployments from the dashboard screen.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Delete…  ·  Admin →

11. Add Migrate options to API Import

    First I want to say that the new API functionality added in latest versions is very appreciated especially the possibility to export/import project out of spaces. However we really miss the merge functionality when importing project from Non-prod octopus to Prod Octopus

    Our current automated procedure includes : Delete project-> Re-import Project-> Update prod variables

    Problems: It removes history and require a new release number in prod due to updated of variables.

    Addition to this feature requests includes: Exclusion of environment variables in export

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

12. Custom advanced variable substitution filters

    Add ability to define custom substitution filters that can run scripts defined by the end user.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

13. 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 single package in the cache would address these issues. I am trying to solve a problem we are encountering when deploying packages from feature branches. We want to be able to have a single release (and therefore package version) per feature branch instead of having to create a new package version (and therefore release) for each new build.

    Right now we are forced to re-download for every deployment, but this is quickly filling up our package cache. We could add more disk space, but at the same time, we don't care about having older versions of the package -- we don't even want to keep these packages around. For feature branches we only care about deploying the absolute latest version.

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

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Delete…  ·  Admin →

14. 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 policy step is executed where the options should be:
    * Let Tentacle decide
    * At the end of the deployment process

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

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Delete…  ·  Admin →

15. Apply the retention policy out of hours (or on a schedule)

    Applying the retention policy at the end of a deployment isn’t the best use of deployment time especially in a tenanted environment with many packages to deploy for many tenants on a single vm.

    I would love to see an option to apply the retention policy out of hours, when the environment is at a low usage.

    It would certainly speed up our deployments.

    Similar to, but using a schdule.
    https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/42726191-control-when-tentacle-retention-policy-step-will-b

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Delete…  ·  Admin →

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

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Delete…  ·  Admin →

17. Dashboard icon page target

    I manage a multi tenant system and the dashboard is always a pain to use.

    First the icon cant be trusted as it dose not accurately show things like a single tenant deploying (The animated icon).

    But the real pain is that if I click that icon it takes me to the deployment page of one of the tenants. What I want it to do is take me to a screen for all of the tenants. Something like the tasks screen filtered by environment would be very nice.

    Then I would be able to see the true state of all the tenants in this deployment and not just a random one.

    And then i can click the necessary icon from that screen to get to the individual deployment details.

    It would be nice to add some screen shots but it looks like there is no easy way to do that here any more. ):

    I manage a multi tenant system and the dashboard is always a pain to use.

    First the icon cant be trusted as it dose not accurately show things like a single tenant deploying (The animated icon).

    But the real pain is that if I click that icon it takes me to the deployment page of one of the tenants. What I want it to do is take me to a screen for all of the tenants. Something like the tasks screen filtered by environment would be very nice.

    Then I would be able to see the true state of all… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

18. Add timeout to guided failures

    Add an option to have guided failures timeout out and fail after a specified period of time. I.E it no manual intervention is taking in 1 hour have the deploy fail completely.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Delete…  ·  Admin →

19. Marking a process step as non critical

    Some steps in the deployment process could merely be just to trigger some notifications or sending metrics to other products. These steps are not critical to the deployments.
    A flag in the step could be helpful which can mark it as a critical/non-critical step

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Delete…  ·  Admin →

20. Allow override of appVersion during Helm upgrade step

    appVersion for Helm charts cannot be overridden with command-line arguments, which means the new version must be overridden before packaging the chart, which causes a new chart version per application version.
    There are workarounds for this, but those cannot be done with the current Helm upgrade step.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →