General
-
Allow non-tenant and multi-tenant deployments to the same environment
The new 3.4 Multi-tenancy feature is great. But there is a limitation preventing it for some to use it effectively.
We have several projects, some have multi-tenant deployments (per client) some others not (tool project, shared services projects etc).
We deploy all these projects to the same test and staging servers and some as well to production environment. Meaning, the same machine might be used for multi-tenant and non-tenant deployments.
The current 3.4 release does not allow us to use the same environment/target for both type of projects.
Workaround as published (setup dummy tenant instance) is a less desirable, as…
91 votesHappy to share that this is now available in 3.15.
See our blog post for more information – https://octopus.com/blog/octopus-release-3-15 -
provide a way to send notifications from failed tasks
as an admin, i'd like to receive email notification of failed tasks such as health checks or other automated tasks.
3 votes -
Deployment Steps Logic
It would be nice to have the option to run different steps based on the status of the previous step (failed or completed successfully). Sort of like an If/Else statement. This way, you can roll back changes if a certain step fails within the deployment process.
4 votesA few months ago we implemented step conditions which covers this scenario
-
Enable PowerShell Debugging only for particular steps/scripts
PowerShell debugging feature uses special variable Octopus.Action.PowerShell.DebugMode which only allows to turn script debugging on and off. Any real deployment contains many steps and many scripts, out of which only one particular script is under debugging, not all of them.
I propose to make DebugMode selective.
One way to achieve it would be to use special variable to configure step name (or a list of step names) where scripts run in debug mode.
Another way (may be combined with the first) is to let PowerShell scripts to invoke debug break explicitly, exactly where and when it is needed.3 votesThis is already possible – the variable can be scoped to the specific step that you want to debug.
-
Expand the size of defect description box and allow for hyperlinks
As part of my TeamCity builds I like to check if a build that ran a deployment has passed/failed (because sometimes a deployment has suceeded but tests run afterwards in TeamCity have failed), and if it has failed then raise a defect via the Octopus API. I like to add the name and link to the build in the defect description.
However, the the max length of the defect description box shortens the message posted. It would be great to see this increased.
Furthermore, if links could be supported somehow then users could click on the link to take them…
16 votesThe defect box no longer trims the text
-
Show the Time of the Deployment on the Dashboard
Include the time the deployment was made on the dashboard
Source: http://help.octopusdeploy.com/discussions/questions/8580
57 votesThanks for your feedback. Sorry this took so long to action.
For the v4 release, we added the time to the title/hover text of this label (which you can use now), but you’ve all raised good reasons about why the time should be shown directly in these deployment/task cells.
Time will be included in the next 2018.5.2 patch release for the dashboard / task cells, shipping early next week.
-
Please have a copy of your W9 on your website.
And please leave a support or contact form so that we can reach out to you with non-technical questions also.
1 voteWe already have our W-8 on our website available for download: https://octopus.com/company/eula
All support requests (even non technical) go to our email addresses also provided on our website. -
Put the SAVE button in the same location on every page instead of upper right of bottom left.
The SAVE button is in the bottom left on the deploy process config page and upper right for the variables page.
8 votesThe save button is now 100% more consistent in Octopus 4.0
-
Enable triggering deploy for entire group
When you got a lot of microservices inside a group, one click to start deployment for all of them in their defaults lifecycle
3 votes -
License Screen - Add Summary
Add a simple summary to the license screen showing how many projects / users / deployment targets are "used" to make it easier to see how much capacity is left in the license and where the capacity is used.
94 votesThis was implemented in version 4.0 – the license screen under configuration now shows counts and limits for all applicable license limits.
-
Certificate Management
We are working on a feature to allow storage and management of X509 Certificates within Octopus.
https://github.com/OctopusDeploy/Issues/issues/2701
If you have any comments or suggestions, please post them to the GitHub issue.
10 votesThis has been implemented: https://octopus.com/blog/certificates-feature
-
Create SemVer 2.0.0 packages with OctoPack
Along with the new changes in 3.4 allowing SemVer 2.0.0 packages to be used, it would be great to also be able to create those packages in OctoPack.
16 votesThis feature has now been provided in the OctoPack build 3.4.1
(https://octopus.com/downloads/3.4.0)
This version of OctoPack, used in conjunction with a 3.4 Octopus Deploy server fully supports SemVer 2.0 -
Create a Swagger site for the REST API
The API is difficult enough to navigate without the ability to quickly test an API call against a URI. Your client api is ridiculously confusing but a swagger endpoint would at least allow us to hit the links for a given resource object directly to see if we are fishing in the correct pond. The current situation is prohibitively painful.
6 votesGreat news! Swagger has been introduced as part of the 3.17 release. See our blog post for more info.
-
Create a Widget for Microsoft Visual Studio Team Services
To create the ultimate overview on your Visual Studio Team Services (VSTS) Dashboard it would be great if Octopus offers a widget where you can see the Octopus dashboard overview for your project.
More information on VSTS Dashboard widgets: https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-dashboard-widget
15 votesThe Octopus Deploy – VSTS plugin now provides a dashboard widget
https://marketplace.visualstudio.com/items?itemName=octopusdeploy.octopus-deploy-build-release-tasks -
Option to not extract packages
The basic request comes down to having a checkbox on the Deploy Package step to prevent Octopus from unpacking a NuGet/Zip/Tar file after pushing it to the target server.
Package to deploy: PackagerName 1.2.4
Target roles: MyServerRole
[x] Do not extract package after pushI'll dig a bit deeper on the reasoning behind the request.
We have a solution we'd like to deploy to a deployment pipeline which we receive from an external vendor. They provide a NuGet feed with their packages. One of these packages contains the installer code and all configuration templates, the other packages are validated and…
49 votesWe have released a ‘transfer a package’ step that does this functionality in 3.7.12 http://docs.octopus.com/display/OD/Transfer+Package
-
Show all projects on dashboard
Love the filter on the dashboard (v3.3.15), however, we have 75+ projects across 6 groups but it only shows the first 50. It's very confusing which of the first 50 it actually shows. I.E. different groups are missing things... It needs to show them all, unless I customize my display. I fear I am going to miss something that didn't automatically deploy - looking for the red box.
18 votesThanks for your feedback. This was addressed in the v4 UI upgrade. We increased the default project limit to 200 (previously 50) on the dashboard, plus we always show any failing deployments now. This setting is configurable in the dashboard configuration if you wish to increase/decrease this limit.
-
Allow the use of F# script (.fsx) in place of Powershell/ScriptCS
Please enable the option to use .fsx files (F# script) in places where Powershell is currently used.
It's concise syntax make it perfect for scripting, it's a darn sight easier to pick up than Powershell, comes with a fantastic REPL and as a bonus the popular F# library "FAKE" provides functions for all manner of deployment tasks and operations.
275 votesThis feature has now been provided in Octopus Deploy 3.4.0 (https://octopus.com/downloads/3.4.0)
-
Add a way to pass parameters when using scripts in packages
In Octopus 3.3 the option to execute a script inside of a package was added, along with a field to declare the name/path of the script.
It might be good to add an extra field (or another way) to pass parameters to these scripts, just like other tools like TeamCity, AppVeyor or TFS have.
42 votesReleased as part of 3.3.21
-
Different icons/images for the new TFS build steps
Currently the new build steps in TFS 2015 for octopus, have the same image/icon and it's not easy to identify which type of step it is.
I suggest create different icons for each type:
- Package Application
- Push Packages to Octopus
- Create Octopus Release
- Deploy Octopus Release
3 votesDone as of version 2.0.6 of the Octopus Extension.
-
Azure Resource Manager Key Vault support
This feature allows users store credentials in a Key Vault (like a password manager) in azure, and the reference those keys from their ARM templates.
This was introduced in the Azure SDK 2.9 in 3/31/1026: https://azure.microsoft.com/en-gb/blog/keyvault-support-for-arm-templates/
At the current Octopus version (3.3.6), this doesn't work. It'll definitely be handy to support this feature.
28 votesShipped as part of 3.3.25. Documentation: http://docs.octopusdeploy.com/display/OD/Deploy+using+an+Azure+Resource+Group+Template#DeployusinganAzureResourceGroupTemplate-SensitiveData
- Don't see your idea?