522 results found
-
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 -
Execute F# script steps using dotnet fsi
Several packages are now incompatible with FSI as it uses the old execution engine, one example is FSharp.Data and latest Newtonsoft.Json. System.Text.Json is also out of the question, basically anything targeting Netstandard 2.0.
Switching to
dotnet fsiwill allow usage of said packages. It will also ensure cross platform compatibility for scripts and allows referencing packages in the script. https://devblogs.microsoft.com/dotnet/f-5-and-f-tools-update-for-june/5 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 -
Variable value scoped to release version
Often times I need to update a configuration variable but, only once we are about to release a particular release.
For example, if I'm upgrading my SQL server and moving to a new machine. I've got a release for the new SQL server version let's call it 2.0.0.0, however, I can't put my new connection string variable into Octopus configuration because I'm still deploying version 1 releases until it's time to migrate.
What I would like to be able to do is specify that the variable for the connection string is X for all releases prior to v 2.0.0.0 and…
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 -
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 -
Deployment Time Option
If you redeploy to Tenant and that tenant is deemed to have the latest version, then the tenant is skipped.
Though the main reason (well for us and many other companies I've worked at using Octopus) is that we simply want to re-apply an updated variable set.
In this scenario:
* I don't want to redeploy the package.
* I only want to re-run the web.config/appsetting.json transforms.Install of just the skip option
(x) Skip deploy...
( ) Apply configuration changes only1 vote -
1 vote
-
Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects
Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects
18 votes -
visualization of build stability in octopus
It would be great if octopus has a project wise dashboard option where we can create visualization of project build stability like status of last 100 deployments , how many passed , how many failed etc
1 vote -
Deployment Trigger Support Multi-Tenant
The Deployment Trigger should support multi-tenant logic. I am sure I do not have a unique environment that a test/staging environment is in a single tenant and production can span multiple tenants.
1 vote -
Allow worker pools to be compatible with ALL process steps
Worker pools only are compatible with two OOTB Octopus process steps (deploy a script, deploy to cloud). My team heavily uses the 'Deploy a Package' step, but this step is not allowed to use worker pools. This is quite an oversight and should be a prioritized feature in the next sprint.
2 votes -
Add date, time and date/time variable types
Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.
Optionally provide a friendly interface (date picker control) for the respective values.
6 votes -
Show worker name in Task Log
Please add the name of the worker machine to the task log when a deployment is made. It is a small change which I think will be easy to add.
Reason/Rationale/Context: We were working without workers/worker pool and we just had a few deployments that we were setting up to run on our Octopus server. My colleague added a worker and without me noticing what I thought was running on the Octopus server was moved to the worker. I knew I had the dependencies my script needed installed via Octopus on the Octopus Server (like a trusted root certificate and…
1 vote -
Execute adhoc data updates with sql on Jira
Hi it would be useful to have execute scripts feature on Octopus for data config changes to be picked from jira.
This will help to select dev env and validate SQL and use as test evidence to run on prod env.
Auditing abilities on octopus can be further enhanced by attaching script execution to Jira also. All major releases have database changes along with binary deployments, it is imperative we keep audit history for data changes also.1 vote -
Allow variable in variable set to have a Project Group scope
It would be useful if we could set variables in a variable set to a Project Group scope.
The use case for this is that we have a shared variable set that sets a product ID.
We could then scope this by product group.
eg
Variable Set Products
Product Id - ATeam Scoped to Project Group A
Product Id - BTeam Scoped to Project Group BProject Group A
- Proj A1
- Proj A2Project Group B
- Proj B1
- Proj B2Currently we have to override the ProductID in every project in Project Group B which sometimes…
2 votes -
Support inserting into an array in JSON Configuration
Given an JSON settings file which has an array element
e.g. { "Users": [] }
Use Octopus variables to insert into the array rather than just replace values.
e.g.
define Users:0:Username = user
define Users:0:Password = passwordWould result in the object getting inserted
{ "Users": [ { "Username: "user", "Password": "password" } ] }
https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7
15 votes -
Deploy a Release Step - Task Summary View
We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.
When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.
1 vote