General
-
Skip deployment steps
I just updated to the new 4.0.3 version of Octopus. I do NOT like the process to skip deployment steps. It is hard to follow and see what is going on and takes way longer than the older versions. Please change this to something more like the older version where I can see all the steps and easily click on the ones I want to skip.
One of the people on my team couldn't even figure out how to skip the steps it was such a pain to find.
6 votesGood news! We’ve improved this part in Octopus 4.0.10 – https://github.com/OctopusDeploy/Issues/issues/3972
-
Excluding steps has become unmanageable
Excluding steps has become unmanageable, please revert to what you had before... causing us hell.
1 vote -
Allow to mark a deployment step as mandatory (un-skippable)
Right now only manual intervention steps cannot be skipped during a custom deployment. It maybe good to be able to mark any step as unskippable.
15 votesThis was implemented in Octopus 2018.4: https://octopus.com/blog/octopus-release-2018.4
-
UI new version - exlude steps awful to use when having many steps
in our Deployment processe we have 25 steps.
on old version we was able to check or uncheck for example steps 1 to 10. in order to deploy first part or second part.but now in the new version the exclude steps is not as esay. you have to open select box, select one step. the selectbox is closed. then you have to open it again and select the next step... 10 times... it is lot longer thant only chech on uncheck visible checkboxes.
i would expected an easier way but now it is an harder way...
1 voteGood news! We’ve improved this part in Octopus 4.0.10 – https://github.com/OctopusDeploy/Issues/issues/3972
-
Search for user
The users view that pages user into n number of pages, makes it a hassle to find a user when you have 100 or more users.
I would like to be able to search for a user, and search across username, displayname and email address.
14 votesThis ability is available as of Octopus 4.0
-
Make "Run on Octopus Server" a separate permission
As it is now if you can change the deployment process, you can also set scripts to run on the Octopus Server. We want people to be able to change the deployment process, but not to run scripts on the Octopus Server. A permission or feature-toggle to restrict that option would be great.
24 votesWe have implemented this in 2018.1 (https://github.com/OctopusDeploy/Issues/issues/4070). However it will be superseded by https://github.com/OctopusDeploy/Issues/issues/4158 in the future (subscribe to that issue to stay updated).
-
Step for docker package selection
As of version 3.7.12 it is possible to use the "Transfer package" step and use the selected package on custom steps (e.g. push it to an s3 bucket).
However, when it comes to docker "packages" the only way to select a docker feed is by using one of the 3 default docker steps.
It would be nice to have a basic step which would allow us to select only the docker feed and have that step export the image+version (tag) to other steps.
In my case, this would allow me control the deployment of a specific image using custom templates…
19 votesThis is now possible with package references from script steps, introduced in Octopus 2018.8: https://octopus.com/blog/script-step-packages
In particular, see the Container Images section: https://octopus.com/blog/script-step-packages#container-images
-
UI new version - release list without comment
we do not see anymore the comment on the release list.
it was helpful to have a small remiinder of difference between versions1 voteRelease notes are now included in the releases list screen since version 4.1.6 (original issue here: https://github.com/OctopusDeploy/Issues/issues/4111)
-
Raspberry pi support
Add raspberry pi support to Octopus and Calamari.
Self-contained version of Calamari is perfect, but it's not possible to use it on RaspberryPi, because Octopus supports now linux-x64 platform and Pi requires linux-arm.2 votesThis is now supported. See the blog post at https://octopus.com/blog/deploying-an-octopus-pi for an example deploying to a Raspberry Pi.
-
Add option to mask sensitive variable while typing it in
While typing in the value of a sensitive variable, the complete value is always visible while typing it in.
It would be more secure if there is an option to obfuscate the value while typing it in.
1 voteAs of Octopus 4.0 sensitive variables are edited masked by default
-
Allow octo.exe to generate results in machine-readable formats (i.e. JSON/XML)
octo.exe is a great tool that wraps much of the Octopus Deploy API. It would be great if we could specify a parameter --output-format=json or --output-format=xml to have octo.exe generate its results in a machine-readable format for further scripting (e.g. in an environment where I have an older version of Powershell without access to modules such as Octoposh).
3 votes -
Allow uploading PEM file containing certificate chain
The Certificate Management feature currently allows uploading certificate chains in PFX files only.
Please also support uploading chains in PEM format.
5 votesPEM files with certificate chains can be uploaded or pasted into the certificate library. The video at https://youtu.be/I01yI-FprMU?list=PLAGskdGvlaw02xL8jUBCF0DirsRZVZrjw has an example of this feature in action.
-
Allow deployment of a project to an environment without any machines in that role
We have a pretty ephemeral environment in AWS and setup new environments several times a week. Our ELB healthchecks are tied to the web apps we're deploying. This can kind of create a timing or chicken-and-egg problem when we need to deploy a project to a new environment. We have to deploy the app for that box before the ELB kills the instance as unhealthy.
What I'd like to be able to do is deploy a project to an environment then as new EC2 instances are registered with Octopus we lean on deployment triggers to deploy the software as soon…
19 votes -
Target machines by Tenant in Script Console
It would be really helpful if I could target a set of tenant machines in the script console.
Sometimes I want to run a script on the machines allocated to a specific tenant, but right now I need to pick those machines manually. That's OK if all my tenanted machines are named using a convention including the tenant name, but with the public cloud that often isn't the case.
What would be lovely is if I could choose one or more tenants and have the script console run the script across all the machines those tenants are allocated to.
Likewise…
9 votesRunning a script against machines associated with a Tenant shipped in 2018.4.1.
If you have a strong use case for using tenant tags here, please create a new suggestion.
-
Tenant Comment / Alert
It would be nice to be able to add notes or an alert to tenants so that we have some warning about release windows or contact people against a tenant.
2 votesDescriptions, in markdown format, can be added to tenants as of Octopus 2019.8
-
Allow scripts to reference NuGet packages
Allow C# and F# scripts to include references to NuGet packages that are downloaded and referenced before the script is run (see http://scriptcs.net/).
Preferably the feed could be any defined feed and not just NuGet.org.
4 votesWe believe this has been addressed by the ability for script steps to reference packages, introduced in Octopus 2018.8: https://octopus.com/blog/script-step-packages
-
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.
- Don't see your idea?