522 results found
-
Pack and Go
Add an option to create a deployment package just like a zip file with parametrizable powershel script file and all packages as a single setup step for non-octopus driven deployment from the deployment steps.
1 vote -
indicate if a release had skipped process steps
we want to quickly identify if a release had skipped process steps.
Some kind of icon or status color.
3 votes -
Decorate overridden config file settings with an Octopus tag (or something)
Some of our services have large config files and we will allow some settings to be defaulted (not configured through the Octopus UI) and others must be configured. I would like a Project Level setting to be included that if enabled would decorate the deployed config file with some indication that Octopus overrode the setting. This would help tremendously to be sure which settings were defaulted and which were set by Octopus.
1 vote -
Allow option to set or override variable values from within a Manual Intervention step
While we make great of environments and machine roles for our production servers and devices, we still find it difficult to manage certain test scenarios without having to maintain a very large collection of test environments in order to mimic each distinct production environment. It would be nice to have an option, at the deploy time, to override or set certain variables, allowing a single test environment that can be dynamically configured to use various settings.
1 vote -
Add ability to specify a minimum powershell version for a step template
Step template should not run if minimum power shell version is not met.
1 vote -
Variables in NuGet package ID per enviroment
It would be great if the NuGet package ID could contain a variable that was resolved on a per environment basis instead of only once when the deployment is created.
We have the same process for each client with a different installer and out current solution has been to package them all into single NuGet package and then grab the correct one on a per environment basis with a powershell step.
4 votes -
Enable a failure/success variable to be used in the email subject
We would like to create one step template that will send an email to the developers with the deploy result.
It would be nice to have a variable like Octopus.Deployment.Result to include the deploy result in the Email subject.
As far as I can see you can not use powershell or the if structures from the Email body?2 votes -
Support ZIP(compression) of files/folders
Most of our deployments begin by first copying existing deployed files/code to another folder as a backup. This is required in case a quick rollback is required.
Would be nice if I could zip those files to save disk space.
2 votes -
Allow Octo.exe create-release command line to specify an alternative NuGet feed than the one(s) indicated on the steps of a project.
Allow Octo.exe create-release command line to specify an alternative NuGet feed than the one(s) indicated on the steps of a project.
We have a DEV feed which is used for all development builds and development deployments. Due to circumstance beyond our control, we cannot have our development environment match all other environments close enough to want to promote releases from development.
We have a MAIN feed that is for all other environments (QA, TRAIN, PROD).
The problem we have is that a deployment step is tied to a specific NuGet feed. This means having to maintain two versions of a…
2 votes -
Deploy without storing a package or release
I want to use Octopus to deploy an application without having to store a nuget package or create a release for it. The reason for this is that some of my automated tests are end to end tests that I run against a deployment in my WiP environment. If these tests fail, I don't ever want to be able to deploy that version of the application. The best was I see to do this is to be able to directly deploy a package through Octodeploy. Once these pass I could potentially create a release from what I just pushed or…
1 vote -
Make OctoPack an developmentDependency
OctoPack is a build time tool not a project dependency.
Adding the developmentDependency attribute will allow other tooling understand this.see http://nuget.codeplex.com/workitem/1956 for more info on developmentDependency attribute.
2 votes -
Add support for a tool library
Currently when we need some tools (sqlpackage.exe, sqlcmd.exe, some DLL...) to be present on the tentacle for our deployment script we create a NuGet package with the tool and have to manually add a Deploy Package step for each tool to deploy it in a standard path so we can then use them from PowerShell scripts/
It would be great to have a tool library:
- we create a tool by specifying a NuGet package, a name and a description
- in each steps (template steps or process steps) we can specify which tools is needed
- when deploying the…2 votes -
Create a step template that applies config transformations
Have an entry field that accepts the same sort of content as is seen in the transform window here: https://webconfigtransformationtester.apphb.com
as well as maybe a file pattern/name to match the transformation to.This way one can avoid building multiple instances of an application, one for each build configuration (environment), transforms don't happen at build time and can take place as part of a deployment.
2 votes -
Enable one to be able to iterate a list of last installed directory paths for steps in project
Create an Octopus variable that contains the last installed directory paths for the steps in the project. This becomes useful if you have one step that deploys and another that works on the previously deployed step, but for some reason you deployed one set of steps first and later the remaining steps.
1 vote -
Display just the variables applied to a release on the release's page
The Variables section a Release page appears to show all variable that apply to the release, would it be possible for any variables which are obviously being overwritten to be omitted from this list?
As an example, if I have a variable in a Library which is being overwritten by this particular project, at the moment both will appear in this list.
2 votes -
Configure Default Deploy Options
It would be nice if you were able to configure defaults for deploy options. Currently they are all false by default. I never really had a need to check any on a regular basis until Guided Deployments are introduced but now I find myself checking this option with every deployment, which isn't optimal. I'm not sure if it would be best to be able to configure these on a per project level or perhaps project group level but it would be nice to configure their defaults somehow.
1 vote -
Add channel to the deploy release page
On the deploy release page (the one that shows just before actually deploying a release) the channel (if any) is not shown anywhere on the page. Would be very useful to avoid mistakes when deploying.
0 votes -
Deploy in "Debug Mode", pause after each step
It would be useful to be able to run a deployment in "Debug Mode", where it would execute one step at a time, pausing after each step, so a developer can verify that it is operating correctly.
0 votes -
If a step failed on a specific Target / Tentacle remove it from the list of targets for future steps
It would be configurable and we could leverage the existing functionality of how the Health Check steps take targets out of the list for future steps.
0 votes -
Provide access to account credentials during deployments
When a deployment is being executed, there may be some value in providing access to account credentials that have already been stored and managed in Octopus Deploy.
While the primary motivating factor for creating the accounts section has been to provide access to deployment targets, some users may get value from using them to access or control other parts of their deployment process that sit behind some authentication mechanism. This would allow OD to better manage all the resources needed to fully complete a deployment with authentication details being securely managed in one place.
The biggest concern with this approach…
0 votes