522 results found
-
Provide the ability to generate cryptographic strong passwords
When deploying application containers, there can be times when you want a password that no human needs to know and survives only for the lifetime of the container.
Our primary use case is generating secure keystores for certificates, etc. At container start-up, it will generate a new local keystore and we then have the ability to dynamically sign CSRs generated within the container via an external signing service.
We do not want to leave the keystore nor the certificate objects without any password, but also do not want to store the values anywhere external to the container.
Granted, we certainly…
2 votes -
Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button
Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button. This is the same thing that Octopus already has for variables. Just do it for Processes!
Nothing worse than having to make a small powershell script change then create a new release and run it back up the runway or having to temporarily manipulate the lifecycle to get it re-deployed to where you want it to go with the updated process.
I want to be able to go to the release. Hit update processes for that release to what I just changed on any process then be able…
1 vote -
Generate a deployment preview to show all variables and machines that will be utilized
I would like to be able to generate a deployment preview without creating a release. I would like this preview to show all in-scope machines and variables that will be utilized given the selected parameters for the deploy. This will help greatly in identifying misconfigured scope for variables and machine roles/environments
2 votes -
Release created date (system variable)
The system variable Octopus.Deployment.Created is updated/changes between deployment to the different environments, but it would be great to have a static value for when the Release itself was created.
So i suggest a new system variable Octopus.Release.Created that says when the release was created (with the Create Release button).1 vote -
Show the Project name on HTML Title instead of "Overview - Octopus Deploy"
When you navigate to a project, you get to the Overview page as a start. When you open up many projects at once (cause a change triggered multiple CI for example, which should be deployed) all of them will show "Overview - Octopus Deploy" in the HTML title and as such it's also what's displayed on the browser tabs:
You loose the ability to distinguish between these tabs. It also means that if you bookmark multiple projects then you'll have to change their title manually to have a valuable label for them. You have to click around them to figure…
7 votes -
Assign Worker Pool(s) to Environment(s)
Rather than using cloud regions it would be much easier to assign a worker pool(s) to environment(s). We have a lot of security requirements and being able to use specific workers per environment would help us tremendously.
5 votes -
Deployment Steps - Loop Step with variable
Hi,
I have a service/container and I want to launch it in the same machine a number of times (variable to be applied per environment/tenant) .Do you have something for this? Can you put this?
6 votes -
Support SemVer 2.0.0 for Channel Version Range, with regex to match build metadata
Semver 2.0.0 support has been added to Octopus, now supporting both pre-release tags and build metadata, e.g.
2.0.0-pre.release+build.info
However Channel Version Range matching has not been expanded to also support SemVer 2.0.0, and still only allow matching on SemVer 1.0.0 components, the version number (range) and pre-release tag (regex).
I suggest you add SemVer 2.0.0 support to Channel Version Ranges, adding a second regex to optionally match on build info.
The will enable users to automatically select and restrict the correct deployment Channel for the type of build.
Use case 1: We have some projects that use opinionated frameworks that…
3 votes -
I have multiple nuget packages that I want to deploy to a single location, can this be done with Octopus Deploy?
I have multiple nuget packages that I want to deploy to a single location (these nuget packages all make up the single Application), can this be done with Octopus Deploy?
1 vote -
Enable worker pool support for 'Deploy a Package' step
We have nearly a dozen client/WPF projects that primarily consist of backing up a directory and then overwriting it with an updated package (size ranging from 20-350MB). Each of these projects push their packages to 20 remote servers, but the servers cannot host tentacles due to our security policies, so we run the steps from one of our Octopus hosts (via tentacle installed alongside the manager service). This is slow and expensive on the Octopus host, especially when there are many other deploys underway. Worst of all, it forces steps to deploy in serial versus parallel because all steps are…
9 votes -
Deploy Release step should prevent picking releases from a different lifecycle
When creating a deployment 'parent' that utilizes the "Deploy A Release" step 'child', it's possible to create a 'parent' release with a 'child' release version that uses a different lifecycle. When attempting to deploy, the following cryptic error is returned:
The step failed: Activity <Child Step Name> on the Octopus Server failed with error 'The release has unresolved defects and cannot be deployed to this environment.
Once you have corrected these problems you can try again.
If the problem is related to a variable you will need to update the variables for this release or recreate the release for the…1 vote -
Allow linking of the Enabled checkbox to a variable
For various steps it would be nice to allow the "Enabled" checkbox to be linked to a variable. For example in the "Deploy to IIS" step template.
This would work just like it does in the website bindings popup, each binding can be linked to a variable.
1 vote -
Scheduled deployments allow select release versions
Hi,
We would like to select certain release versions in the scheduled deployment triggers similar to how we create a new release and can select a release version
Currently it doesn't seem to be possible and it uses only the latest release
Hope this can added in the next Octopus release
Thanks,
KK6 votes -
Performing dry run with octo.exe push (--whatif)
Looking at the documentation for “octo.exe push” (https://octopus.com/docs/api-and-integration/octo.exe-command-line/push), but I cannot see any option to perform a dry run. The ‘create-release’ command has a ‘whatif’ param, and it would be really handy to have this on the ‘push’ command as well.
8 votes -
Have Tenant name fully display on Infrastructure page without hovering
It would be helpful if you could have the Tenant name display on the Infrastructure page under Deployment Targets instead of hovering.
1 vote -
Upload of environment variables from .env
I think it would be nice to have this feature on Octopus.
So I was given a deployment task and I had multiple environment variables to upload.
I am the lazy type so instead, I wrote a python script to enable me to upload all at once in just a sec.I hope this saves someone too
2 votes -
Make deployments synchronous for a specific environment
I help manage deployments for a software team that is working on moving from bi-weekly releases to continuous delivery. In order to transition smoothly, we have decided to have four environments in our pipeline: Dev > Alpha > Beta > Production. This allows us to continuously deliver internally from Dev (automatically deployed to from build server) to Alpha (snapshot of all projects promoted to Beta bi-weekly for staging).
What I would like to have the ability to do is make all deployments to Dev synchronous in that they wait if there is a current deployment to Dev and stay pending…
1 vote -
Add a step to allow deployment of a template to create Subscription level resources in Azure
Azure allows for the deployment of Subscription level resources via a template, but currently there is no out of the box step to do this in Octopus.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/deploy-to-subscription
It would be great if we could have a built in step, along the same lines as the 'Deploy an Azure Resource Manager' template step.
1 vote -
chained deployment to specific targets
If you deploy to specific targets in an environment but one the steps triggers a chained deployment, the chained deployment will target all hosts in the environment. It would be better if the chained deployment continued to target only the specific hosts that were originally chosen.
1 vote -
Ability to diff variables against previous release when deploying to an environment
Scenario: I am about to promote my new release to production. My release is clean (i.e. I'm not getting the "something has changed warning"). However, a week ago, someone made an errant change to the production transform for a shared library set variable. If I deploy, it will break due to that variable change that I don't know about. I don't have a good way to detect this before I hit deploy.
Request: On the deployment screen for a release, provide the ability to diff that release's variable snapshot against the variable snapshot from a previous release that was deployed…
12 votes