522 results found
-
when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run
when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.
idk what you call this icon with the orange square and white lightning bolt
but when the lifecycle is in this state, the save button really means, “go ahead and run”.
1 vote -
Allow structured variabel replacement in the Upgrade a Helm-Chart step
This would be useful for replacing values especially in the values-file from Chart Package or Additional Package. With this feature we don't need to have variable replacement syntax in our source-files.
6 votes -
Add Deployments link to Worker View
Add Deployments link to Worker View like what exists for deployment targets
Deployment target link path example: /app#/Spaces-1/infrastructure/machines/Machines-xxxx/deployments
2 votes -
Add Migrate options to API Import
First I want to say that the new API functionality added in latest versions is very appreciated especially the possibility to export/import project out of spaces. However we really miss the merge functionality when importing project from Non-prod octopus to Prod Octopus
Our current automated procedure includes : Delete project-> Re-import Project-> Update prod variables
Problems: It removes history and require a new release number in prod due to updated of variables.
Addition to this feature requests includes: Exclusion of environment variables in export
1 vote -
Grouping variables in Octopus UI
As a project leader I should be able to group variables on Octopus UI. This can be just logical separation.
This solve the problem with linked variables and help mange them.
For example It could collapse elements that are in structure - for example: db.username and db.password can be collapse as elements of root db or by labeling variables and then can be filtered by using specific label, for example - db.
4 votes -
Custom advanced variable substitution filters
Add ability to define custom substitution filters that can run scripts defined by the end user.
1 vote -
Built-in Azure App Service/Function Restart
I find that deployments to Azure Functions and standard app services will occasionally fail due to files being locked. This usually requires stopping the app service, re-running the deployment, and then restarting the function or app.
This can be scripted with Powershell, but since this is such a common scenario, I’d love a checkbox built into the Azure App Service step that provides this ability. Something like “Stop App Service prior to deployment and restart after deployment”.
3 votes -
Dashboard should be better at visualizing multiple tenants
Currently the home dashboard displays tenants as a small grey-on-grey count of up-to-date tenants vs total tenants. It would be nice to see a coloured pie chart or similar visualization instead, to make it more obvious when one tenant in an environment is still running an old version or has had a failed deployment.
It can be easy to miss failed deployments from the dashboard screen.2 votes -
Support sharing of variable sets and script modules across spaces
https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4
We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.
We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in…
7 votes -
Dashboard icon page target
I manage a multi tenant system and the dashboard is always a pain to use.
First the icon cant be trusted as it dose not accurately show things like a single tenant deploying (The animated icon).
But the real pain is that if I click that icon it takes me to the deployment page of one of the tenants. What I want it to do is take me to a screen for all of the tenants. Something like the tasks screen filtered by environment would be very nice.
Then I would be able to see the true state of all…
1 vote -
Allow override of appVersion during Helm upgrade step
appVersion for Helm charts cannot be overridden with command-line arguments, which means the new version must be overridden before packaging the chart, which causes a new chart version per application version.
There are workarounds for this, but those cannot be done with the current Helm upgrade step.1 vote -
1 vote
-
Add Support for More Runbook Triggers
The only Runbook trigger right now is a scheduled trigger.
I would like to suggest two more trigger types:
Helm Chart Package Trigger:
When a new Helm Chart version of a package is published, then the trigger would fire. (Allowing the calling of a Runbook.)
Version Control Trigger:
If Octopus Deploy added a VCS trigger, then it would allow us to use GitOps.
Both of these allow Operations to enable control from check in / merge point in source control.
1 vote -
OctopusBypassDeploymentMutex for Script console
Parallel execution should be enabled or can be switch on the fly in script console. Via a variable, similar to OctopusBypassDeploymentMutex
With the scenario that there is a process running (read: stuck/looping) in the target and executing a kill command via the script console will get you “waiting for script to finish in task…” so it is currently not the workaround.
Ref case:
https://help.octopus.com/t/force-stop-a-step-execution/26682/32 votes -
Support for .env files with Structured Variables
We are currently using React, Gatsby and Parcel which all use .env files for their environment variables
https://www.npmjs.com/package/dotenv
Currently .env files are not being recognized, they are assuming they are yaml files, which they are not, they are read similar to java properties as key values
Right now we have to use variable substitution, but would like to use structured so we don't need to add #{} tags in our code
1 vote -
Download package option to only keep latest in cache
There are currently 2 package download options when deploying a release: using the package from the cache and always re-downloading. Both of these are useful, but each has one big downside that I think this feature would correct.
When using the package cache, Octopus will never pick up changes that were made to the same version of the package. If forcing a re-download, the package cache can quickly fill up, especially with multiple development teams (and yes, we have retention policies configured -- our packages are unfortunately quite large).
A new option that will just always re-download and keep a…
2 votes -
Add First Class Support for Blue Green Deployments
For a product that is all about deployments, not having first class support for Blue Green deployments is.... odd.
Not a lot is needed. In fact you can't put in too much or it will be too opinionated.
Basically, all that is needed is something similar to your "tenant" system with a blue and a green line. But also show on the line which one is currently in use.
The "in use" flag will need a bit of effort as it can be a percentage or a list of users or both. But that is not too difficult to show.
…
1 vote -
Fuzzy Variable Matching
Allow replacements to be made over different files which share the same structure, but at a higher level requires a fuzzy match.
This would allow us to have a singular variable for repeated applications and the change would be applied to all json files that share the same structure.
Please see the support question below for more specific details.
1 vote -
Add timeout to guided failures
Add an option to have guided failures timeout out and fail after a specified period of time. I.E it no manual intervention is taking in 1 hour have the deploy fail completely.
2 votes -
Bindable variables for certificates in the kubernetes deploy container step
https://help.octopus.com/t/kubernetes-certificate-variable-binding/26581
In the kubernetes deploy step for the certificate field I have a need to use my own single text box bindable template variable rather than the current selection of certificate type only variables. The reason being that this cannot be scoped across both tenants and environments.
1 vote