I'd like to be able to right click "links" and open them in new tabs, etc.
During the 4.0 front-end rewrite using proper links was kept in mind.
For example create a category called Marketing, and then be able to add projects to that category, so that the dashboards can be cleaner and will easily be able to see what's running where.3 votes
Thanks for the suggestion, this has been implemented in version 1.1
It would be nice if you could set up global variables that apply to all projects, to set things like common logging connection strings or debug settings that should always be OFF in production etc.145 votes
This is now supported in Octopus 2.0. Thanks for the suggestion everyone!
Rather than directly associating machines with projects, you should be able to place machines in roles (buckets), and assign projects to deploy to those roles. This allows deployments using cloud providers to scale easily (you don't need to updates dozens of projects whenever you add/remove a machine from production).6 votes
This has been supported since 1.1
As a twitchy release manager (or someone with a defective mouse), I would like it if Octopus prevents me from clicking the "Deploy Release" button twice or more in succession, so that I do not inadvertently screw up my release environments4 votes
Thanks for the suggestion, we fixed this in Octopus 2.0 so it should no longer be an issue
I work in a global team and could only consider Octopus if it had role based security. e.g. Only people in certain roles can deploy to certain environment.1 vote
Seems the "Auto-purge Tentacles" backlog item didn't make it to uservoice and haven't seen a release with this feature...18 votes
This has been supported for some time (as “retention policies”)
Octopus 3.0 shipped today with a much more compact dashboard. Please have a play with it and let us know what you think!
Example here: https://demo.octopusdeploy.com/app#/
Given a project name and an environment, I'd like to be able to query the /api/ area to find which release was most recently deployed.
I'd also like to filter the query to exclude deployments that failed and to exclude deployments that skipped one or more steps.7 votes
Thanks to a contribution by Chris this has been supported in a few releases now.
When adding a new step package typing the name of the nuget package should be case insensitive when offering the drop down help.0 votes
The input is now case insensitive
Azure VM roles are already supported. Add support for Azure web and worker roles.69 votes
As a user, I want to create my own dashboard and share it with my team, so that we can easily see the projects that matter to us.23 votes
Since Octopus 2.0 it’s been possible to modify your dashboard, so I’m going to close this one. Thanks for the suggestion and for voting everybody!
Done in 2.4!
As a package author, I'd like to be able to return variables from my PowerShell scripts in one deployment step, and have them passed to the next deployment step as inputs, so that I can pass useful context information from one step to another.13 votes
This has shipped; results of Set-OctopusVariable will be carried through to subsequent steps as Octopus.Actionname_].Outputmachine_].variable.
Instead of Octopus acting as a client to the Tentacle, have Tentacle connect to the Octopus over Azure Service Bus, to reduce the need for firewall changes10 votes
Polling Tentacles are now supported in Octopus 2.0
We added this some time ago – it’s called:
Support F# as an alternative to PowerShell4 votes
This is now available with rolling deployments
Proxy support is now available
- Don't see your idea?