522 results found
-
Environment specific deployment time slot
Our developers are allowed to deploy to QA 24/7, but only to production in a specific time slot Monday-Thursday from 8-11am.
Could be cool if this was a environment specific setting in Octopus. Each team should have unique values for this setting.
13 votes -
Deployment Email Preferences by User
Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.
12 votes -
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 -
Allow the use of C# script (.csx) using .NET Core
ScriptCS will no longer be supported under .NET Core.
Please enable support for dotnet-script (https://github.com/filipw/dotnet-script) so that C# scripts can be executed under .NET Core
12 votes -
group/filter release list
We normally have builds and releases for two concurrent branches: develop and master. These are distinguished by version number. Currently for example master is on 3.8.0.x and develop is 3.8.1.x. Most of the time new release packages are only generated for develop, but occasionally a hotfix is needed and we get a release package for master.
The list of releases in Octopus Deploy is sorted chronologically, so the releases for 3.8.0.x and 3.8.1.x are all in one long list. It can be pretty hard to find the one lone 3.8.1.x release in that list when we want to deploy the…
12 votes -
Add tenant tag support to runbook scheduling
Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.
11 votes -
Prompt Variable Validation (via Regex)
Often the valid set of values for prompt variables are limited. It would be great to be able to add a regex against which the value could be validated in the UI before executing the deployment
11 votes -
Improve Variable Substitution Feedback/Logging
Currently the information included in the logs, regarding variable substation is very limited:
Performing variable substitution on <filename>
This could be improved in a few ways:
- Add the number of variables substituted to the logs
- Include the variable, and value substituted as Verbose (Sensitive values replaced with stars)
- Add the variable names substituted to an Output variable; I could do my own lookup of the value, and email a report in a follow up script stepIn the end, I'm just looking for some way to verify an integral part of deployments.
11 votes -
Staggered Deployment
the ability to deploy to all tenants (or a group of tenants), but with a specified delay between the start of each deploy.
we have 12 tenants for our enterprise and deploy to our QA and Staging environments nightly. It's convenient now to have a single Octo.exe command start deployments to all tenants, but having them start simultaneously causes a bit of a traffic jam. We would like to be able to stagger the start of each deploy by, say, 5 or 10 minutes. (of course, once 5 deploys are running, the built-in throttling takes over.)
11 votes -
Assign machines to a channel
We have a situation in which we need to restrict the deployment of version N+1 builds from deploying to version N environments. It would be very useful if we could use channels to restrict which machines get deployed to from a given channel. Currently, we have to create a new environment group (future.stack, hotfix.dev, etc), add deployment targets to the new env. group, create a lifecycle to reflect and then assign it to the channel.
11 votes -
Add the option to disregard pre-release packages when creating a release by default
I noticed that when creating a release pre release packages show up in the latest column when their version number is the highest available.
Pre-Release version are usually used for (feature)branches, hotfixes or alpha/beta version of new major releases. All things that deviate from the regular release flow.
I would prefer having to pick the special version using the specific version picker and only see the latest non pre-release version
in the "latest" column on the "create release" page.A simple checkbox to turn that feature on/off on the projects's settings page would do. That way you could set it…
11 votes -
Simple way to publish .nupkg files to Nuget.org
Ability to deploy a nupkg bundle (myCoolOssProject.1.0.0.0.nupkg) up to http://nuget.org whilst being able to leverage the
Promotefeature built into Octopus.I've tried this using a standard approach, but nesting nupkg files doesn't appear to be supported by nuget.exe
Cross Post:
http://stackoverflow.com/q/23317526/12406911 votes -
Allow for specific files that were added by OctoPackEnforceAddingFiles, to be excluded in package
I cannot not use /p:OctoPackEnforceAddingFiles=True with MSBuild. This parameter is absolutely indispensable. It is not even an option.
However I do not want all the files in the build to be included in the package.
The nuspec file and the exclusions ability therein does not allow to exclude files that were added by OctoPackEnforceAddingFiles.
The effect of this is that I can’t use one of the best features of Octo : deploying to IIS.
Because of a few files that I can’t exclude from the build, I need to deploy to a folder, remove the files that I want, and…
10 votes -
Support for percentage on rolling deploy window size
It would be nice to be able to set the window size of a rolling deploy on a certain percentage.
This helps in scenarios where machines are added and removed dynamically according to load (e.g. AWS Autoscaling)
Practical example, I have an ASG that varies from 4 to 16 machines.
The optimal case, is to deploy on 25% of the machines at any time.
10 votes -
Smoother offline package drops
Ideally the workflow would be
1) Push "deploy" in octopus
2) Wait
3) Download .zip from server
4) Unzip
5) Run script
6) DoneTo achieve this, I see the following features as needed
- Allow different target folders (eg. FTP, S3)
- Zip up the package
- Allow decryption password to come via environment variables.An optional extra would be to reduce the size by having calamari separate, but that's not a big deal.
10 votes -
Allow for display and edit of offline variables at deploy time
Offline deployments may target environments that are uncontrolled. This may also mean that there is no information available about that environment such that variables cannot be configured in Octopus Deploy. The result is that the variables must be manually modified on the target environment in config files for each deployment step.
Ideally there would be a UI as part of the offline deployment execution where unsecured variables can be viewed, and all variables could be modified prior to executing the deployment.
10 votes -
Support variable prompting for offline deployments
The current offline deployment comes with the assumption that the target environment is known. We have dev, test and staging environments that we control. Unfortunately we don't control production due to security constraints. We also have a lack of visibility into that environment such that we don't know the variables for production (like database server names, usernames and passwords).
It would be great if a variable could be marked as "Prompt" such that the offline deployment execution can ask the user on the console for the variable values for the keys marked as Prompt.
10 votes -
Add an option to the Windows Service feature to have a Custom User with no password in order to support Group Managed Service Accounts
The existing Windows Service feature supports the configuration of a "Custom User" for the Windows Service to run as
However, it doesn't support the option of having a "Custom User" without password. This is required when using Group Managed Service Accounts (https://blogs.technet.microsoft.com/askpfeplat/2012/12/16/windows-server-2012-group-managed-service-accounts/) which improve security and remove password management for service accounts.
It would be great if the Windows Service feature added a new "No password" check box close to the existing "Change password". If "No password" is selected then sc.exe should be called with no "password= " argument.
10 votes -
Follow channel version rules also with 'Automatic release creation' not only with manual release creation with multiple packages
It would be nice to have the Automatic release creation when attached to a specific channel with package version rules applied to follow this rules to select all the packages, not only the package selected to triggered.
From support forum I've got a reply about it is not possible to know which pre-release tag to use, so they use always the last no pre-release tag.
But if the channel have a rule to use a specific tag to all the packages. The expected behaviour is to select that pre-release package instead of the non tagged (which is actually more confusing)…
10 votes -
allow skipping manual deployment steps
When I click to "skip all" steps in a deployment, I expect "all" to really mean all. Currently all automated steps are unchecked but manual steps cannot be unchecked.
Our normal deployments include a few manual steps such as "Install Windows updates", "execute manual smoke tests" etc. Our patch releases include none of these. Patch releases would be significantly smoother and faster if we didn't have to sit and monitor the deployment and click OK for the manual steps that we are not running.
10 votes