1458 results found
-
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 step2 votes -
Add link/URI within the Octopus, deployment output to support one-click access from CI/CD tools
If you use an Octopus, build/pipeline task within Azure DevOps Server/Services (or another CI/CD tool) to trigger a deployment, it would be useful to have a URI within the feedback output by the deployment within the Azure DevOps (or other CI/CD tool) build/pipeline.
This would allow the Octopus deployment to be accessed via a single click of that URI (as opposed to having to navigate back into Octopus and find the project, the release and then the deployment).
1 vote -
Deployment Time Option
If you redeploy to Tenant and that tenant is deemed to have the latest version, then the tenant is skipped.
Though the main reason (well for us and many other companies I've worked at using Octopus) is that we simply want to re-apply an updated variable set.
In this scenario:
* I don't want to redeploy the package.
* I only want to re-run the web.config/appsetting.json transforms.Install of just the skip option
(x) Skip deploy...
( ) Apply configuration changes only1 vote -
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-b3 votes -
Add filter for the dashboard for failed deployments
We have a continually growing set of projects and some times I want to look through to see if any have failed so I can head off any issues before they become blocking for a team
I would loke to be able to set a quick filter on that dashboard to only see projects with a failed deployment. It could be a simple as a checkbox or toggle button1 vote -
Allow runbooks to be configured not to run immediately after a missed scheduled trigger
Runbooks can use triggers to start on schedule. If the OctopusDeploy service stops for any reason, a runbook that has missed its schedule will run as soon as OctopusDeploy become available. This is suboptimal where the missed trigger was powering off some VMs overnight and runs during your core hours, for example. This behavior should be configurable, much like the "Run task as soon as possible after a scheduled start is missed" setting in Windows scheduled tasks.
1 vote -
1 vote
-
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.
6 votes -
Recognise when a variable is used for a feed ID or package version.
When using a variable to specify a package feed, or selecting package versions for a release, after creating a release Octopus displays an error on the release page.
With regard to the feed ID, it is possible to set a feed ID from variables as discussed here - https://octopus.com/docs/deployments/packages/dynamically-selecting-packages
With regard to versions, it is possible to set a version from variables, allowing the version of a package to by dynamically updated. This is most useful on occasions where another Octopus deployment is triggered as part of the process.
However, even though both scenarios works, after a release is created…
2 votes -
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 -
Allow variables to be set as Environment Variables
It would be extremely useful to allow variables to be set as an environment variable before the process starts (and even allow outputs to be made environment variables). At the moment it is extremely hard to write generic scripts for both development and for use in octopus.
Allowing variables to be set as environment variables eliminates this issue as well as allows more providers etc.
If I take a terraform run where the provider (say digital ocean and terraform cloud) can be initialized via environment variables I do not need to litter my scripts with octopus only if conditionals. They…
2 votes -
Allow Users to Define Their Own Default Task Log View Settings
When viewing a task log you offer 3 settings:
1. Expand
2. Log Level
3. Log tailThey default to Interesting, Info, Last 20
In my position, those settings are almost always unhelpful - I have to change the selections with every task log I view, and in my position I view a ton of them a day.
I'd like the option to set my own personal Task Log View default values so that when I click on a task log my preset selections are automatically loaded and the task log is in my preferred state on page load.
2 votes -
visualization of build stability in octopus
It would be great if octopus has a project wise dashboard option where we can create visualization of project build stability like status of last 100 deployments , how many passed , how many failed etc
1 vote -
Variable value scoped to release version
Often times I need to update a configuration variable but, only once we are about to release a particular release.
For example, if I'm upgrading my SQL server and moving to a new machine. I've got a release for the new SQL server version let's call it 2.0.0.0, however, I can't put my new connection string variable into Octopus configuration because I'm still deploying version 1 releases until it's time to migrate.
What I would like to be able to do is specify that the variable for the connection string is X for all releases prior to v 2.0.0.0 and…
2 votes -
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 -
Immutable Step ID
Similar to most other entities in Octopus (e.g. Projects, Machines, Feeds, etc), it would be very helpful if the steps of a deployment process or runbook had an immutable and unique ID in addition to their display name. This would make referencing a step from elsewhere (e.g. reading output variables) a lot more resilient to change over time.
1 vote -
Depreciate Variable Sets
Variable sets cannot be deleted until all project, release, and I assume runbook references are removed. Since it can take a long time for releases to age out, a Depreciate flag that can be set once all Project references are removed would be great. This flag would prevent adding the Variable Set to projects (and hidden from the selector).
1 vote -
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.
14 votes -
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…
5 votes -
Deployment Trigger Support Multi-Tenant
The Deployment Trigger should support multi-tenant logic. I am sure I do not have a unique environment that a test/staging environment is in a single tenant and production can span multiple tenants.
1 vote