General
-
Icon vs Detail list view
We have a lot of projects 50+ and a lot of hosts 200+ so it's a problem with the big icons (they got even bigger in 3.0)
hard to get an overview.
so make a drop-down where we can select Icon or Detail view (like in the explorer)
Atm there is a lot of mouse wheel scrolling happening to get to the host in the end of the list.22 votesThe project and infrastructure pages have been redesigned from the 4.0 release
-
Mix Domain / Local Accounts
We have an environment where there are a mixture of employees / vendors who need different levels of access to different resources in Octopus. No problem. However, I've got a mixture, some who have just local accounts in our Gitlab & Octopus environment, and those who have AD accounts because they use Gitlab, Octopus & other resources in our environment. If it were possible select whether an Octopus user authenticates off of AD or local, that would be MOST EXCELLENT!
1 vote -
Preserve file timestamp when extracting packages
Many parts of the internet infrastructure use timestamps, but when Octopus extract files from NuGet packages the original timestamps are overwritten with the time of extraction. This causes pain with load-balancers, edge caching, file sync...
It would be very (very very) nice if Octopus would maintain the original timestamp from the original file upon extraction.
6 votesThis was shipped in Octopus 3.4. We have automated end-to-end testing in place which guarantees the desired behaviour as long as you use the tools provided by Octopus Deploy for creating packages, or another method which preserves the file time stamps. Some packaging techniques lose the original file timestamps.
-
Support for Azure Service Fabric
Please support deployments of the new Azure Service Fabric "microservice" architecture platform.
See http://azure.microsoft.com/en-us/documentation/articles/service-fabric-overview/ for the initial documentation and Channel9 build videos.
557 votesHi everyone. Service Fabric support has now been added in release 3.13.0. Please see [the blog post](https://octopus.com/blog/octopus-release-3-13) for details.
We look forward to hearing your feedback!
-
Allow deployments to target roles that don't exist (yet)
Presently Octopus assumes the deployment environment must exist before the project is setup - because you can't create a deployment that targets a role that doesn't exist.
This means that you can get into creating your new deployment, then realize you are blocked from saving, then lose your changes as you a) go and create a role or b) go and talk to the admin (the drop-down won't refresh, so creating the role in a different browser tab doesn't work).
I think it'd be better if you were just warned if targeting a role that didn't exist, but allowed to…
4 votes -
Allow a retention policy for the PackageCache
For Packages I can define a retention policy. However I observe the disk space usage keeps increasing and runs out of space once in a while. The reason is that the PackageCache with .octosig and .octodelta files never gets cleaned up. It would be nice if the retention policy could maintain an acceptable size for the PackageCache as well.
5 votesAdded in 3.2.21
-
Overview of deployment targets
I want a GUI that can answer the question of how many tentacles/deployment targets do we have and what's the health status for them.
3 votesOctopus 4.0 now provides an overview page in the Infrastructure section that looks at Tentacles as a single list without environment grouping/duplication https://demo.octopusdeploy.com/app#/infrastructure/machines
-
Built-in AWS support (like for Azure)
Improve Amazon Web Services integration by adding built in support for AWS.
Example: give your AWS credentials to Octopus and him will create automatically an instance with a Octopus tentacle installed on it.
38 votesIn Octopus 2018.2 we added features that brought AWS support to parity with Azure: https://octopus.com/blog/octopus-release-2018.2#aws-support
This included AWS Accounts in Octopus, and a bunch of built-in steps.
We’ll close this suggestion (so you get your votes back), and any more specific AWS requests can be raised separately.
-
Octopus step templates linked with github
We currently are writing many powershell scripts to work with octopus deploy as part of our deployment and then having to keep a copy in our github repo to be used by the devteam. I'd like a way for octopus to have access to the repository and notice there are changes and allow for a manual update, as it currently works.
17 votesSourcing scripts directly from GitHub is now available in 2018.3.0
https://octopus.com/blog/github-feed -
Lifecycle: Optional phase or optional environment
As a user I would like to have lifecycle phase or environment within a phase be optional.
Use Case:
We have dev test environment which our devs can test stuff before sending it to QA but they are not required to and only usually do so for more complex stories. They also sometimes do ...interesting things with that environment. They need to be able to deploy without restriction or impact on state of other environments.Our QAs however are required to deploy to QA before deploying to staging/prerelease.
Possible solutions:
- Optional phase
- Optional environment in phase that does…163 votesThis feature was released in version 3.12.8.
-
Proxy support for Server/Tentacle Communications
The Halibut protocol used by Octopus Server/Tentacle to communicate with each other doesn't support proxy servers.
41 votesThis is complete and available for testing in the 3.4 beta.
-
Deploy to Azure ServiceFabric
Although service fabric is only in public preview, it's likely to be GA early 2016. For us it's something we want to start using ASAP, so it would be great to have out of the box support for from octopus, rather than us having to craft our own powershell deployments.
1 vote -
Allow variables within variables
Allow the use of variables within other variables. I understand this could become problematic if abused (circular references, etc). However, I think this would greatly simplify administration of large projects/variable sets. For example:
{Administration.Service1Uri} = "http://myhost/service1"
{Administration.Service2Uri} = "http://myhost/service2"
etc...
This could be change to
{Administration.Service1Uri} = "#{Administration.BaseUri}/service1"
{Administration.Service2Uri} = "#{Administration.BaseUri}/service2"
These variable now become target netrual, meaning they don't need to be duplicated when a new target is introduced. Simply duplicate #{Administration.BaseUri} for the new target, and the rest will just fall into place.
Another example would be database connection strings, which typically are identical…
0 votesThis is already supported
-
Move steps as child steps into another step
On refactoring process steps, it sometimes bugs me to delete a main process step and recreate it as child step.
It would be very nice to move a main step "into" another step as child step. Maybe by allowing reordering steps in the complete hierachy?
75 votesThanks for voting on this feature. Happy to share that this was released in Octopus 3.5.7.
-
Azure Deployments using service principals instead of management certificates
Add support for using service principals instead of management certificates for deployments into Azure. This allows more granular control over the permissions octopus has.
http://blog.davidebbo.com/2014/12/azure-service-principal.html
8 votesThis feature has since been implemented from Octopus Deploy 3.3 http://docs.octopusdeploy.com/display/OD/Creating+an+Azure+Service+Principal+Account
-
Extensibility endpoint for custom authentication mechanisms
If we currently look in the current uservoice we will find many items regarding "Azure AD support", "Crowd SSO" or even "Two factor auth". I honestly thing that a simple way to enable those scenarios is to add an extensibility point for authentication mechanism.
This will allow custom authentication (not AD or user/pass) be handled separately and advance in their own. I can see many scenarios around this, including teams and external handling of users with custom databases.
For example, in our organisation we handle developer teams around the Github organisation so when a new user arrives it is just…
5 votesAs of 3.5 there is an extensibility mechanism in Octopus Deploy server. Authentication has been the first area where we’ve provided extension points.
See https://octopus.com/blog/octopus-deploy-3.5 and
https://github.com/OctopusDeploy/Issues/issues/1737 for more info. -
Have Write-Warning in Powershell trigger a warning
Short version:
Have the Write-Warning command in Powershell to trigger a warning in a step and write the warning message.
Long version:
I would like an easy way to write change a step's state to pass with warning. I understand that the current workaround is to use Write-Error with the [-ErrorAction Continue] option, but this also seems unnatural because it prints error messages in red, whereas I would prefer to just write warning messages in orange.
The Write-Warning command in powershell seems like an intuitive candidate to achieve this, as it technically doesn't write to StdOut but StdWarning (can be…
19 votesWrite-warning has been working like this for a while now. Marking the suggestion as "Completed
-
Add Copy feature to deployment step along with Edit, Delete and Child Step
It would be a great feature if deployment steps can be copied within same project and to different project's deployment process.
85 votesCloning Deployment and disabling steps within a project currently exists in Octopus as of version 4.0
-
Better Mobile Views\Layouts
Just upgraded to 3.0. Love the new features. One thing I did not do before but am now doing is monitoring deployments from my phone. I may kick something off before I leave the office and check it when I get home or wherever I am going on my phone. The current layouts do collapse down for a mobile view but they are not very consistent and the grids are hard to navigate. Navigation features (outside of the main menu could use better placement). It would be great if the mobile layouts could be improved when using small form factors.
5 votesNow available in 4.0
-
Environmental setting to immediately start a deployment upon tentacle creation/discovery
You can provision servers and set them to automatically be discoverable. Upon this discovery, I'd love to be able to deploy the latest release to the rest of the environment onto that newly created server.
I'd envisage the option to be callrd something "Automatically deploy latest package to new tentacles".
Reason : I am having to provision servers in AWS as tentacles and then (still not confirmed as doable for my scenario) having to query the API for the machine names to force Octopus to only deploy to these newly created servers (I.e. not do a complete environmental deployment)
18 votesThis is now available as of 3.5 as part of our subscriptions feature.
https://octopus.com/docs/administration/subscriptions
- Don't see your idea?