-
Manage VPN connections
Make it possible to put machines into a VPN connection, and have Octopus manage the closing/opening of the connection so that concurrent deployments don't result in closed or hanging connections.
27 votes -
Search/Replace Virtual Network node in Azure cloud configuration file
In the Cloud configuration file for Azure deployments you can specify VirtualNetworkSite to determine which network the role will be deployed to. It would be great to be able to specify this in Octopus.
An alternative is to specify which service configuration (default Cloud) to use for the deployment/step.
3 votes -
Latest release should be highlighted.
The latest assembled release should feature more prominently on the releases page, at present it is at the top of the recent release list, but it does not jump out at you, The latest release should appear to the left of the currently released versions. when you click it you should be taken to the deploy page.
3 votes -
Add richer dashboard experience by allowing user to promote, create releases and detect changes.
On the dashboard, when hovering over a successful build an arrow should appear next to it with the word 'Promote' clicking this button should start the deployment to the next environment in the chain.
On the dashboard, when OD detects there is a new version available on the nuget feeds, a small + symbol should appear next to the project name, clicking this should take you to the create release screen.
7 votes -
Add an update command to Octo.exe so that it updates itself with the latest version of Octo.exe
It would be nice to be able to run Octo.exe update-self or something like that to get the latest Octo.exe isntead of going to the website and downloading the latest version.
4 votes -
Show Child Tasks On Task Summary/Task Progress
When monitoring a Deployment, it would be nice to see the progress of child tasks that are executing or have finished executing.
4 votes -
Allow "Instructions" on manual intervention step to contain variables
The instruction field on a manual intervention is currently limited to just hard coded text. It would be helpful if it could display variables from a deployment. This would allow me to:
1) Run a script which:
1a) gets the current deployed version
1b) gets the new version being deployed
1c) contacts our build tool (Teamcity in my case) to get information on the changes involved in the build
1d) create a list of hyperlinks to each change between the two versions.
2) Contact our ticketing system to get the details of the release
3)Display those links to the code…16 votes -
Make Tentacles auto configure the disable flag on shutdown.
When the tentacle service shuts down, the polling tentacle would change the machine.isdisabled = true. When the service starts it would set the isdisabled=false. this allows cloud based infrastructure to dynamically turn off machines without having the deployments fail because the machine is turned off.
5 votes -
Delete files when Octopus Deploy is uninstalled from a machine.
Normally, Windows Uninstall removes all program files, except those that have changed since the install (like config files and data files).
Currently the installer does not do this.1 vote -
Make Octo.exe trace logs to the console
It would be great if Octo.exe could trace log output to the console window - instead of waiting for deployment. We integrate into a Continuous Delivery server (not Team City), and it would be good to be able to view errors in one place.
1 vote -
Make TeamCity plugin a seperate step
The implementation of the 1.6 TeamCity plugin just has it as an extra setting under VisualStudio build step. It would be great if we could have this as a seperate build step.
We would like to be able to build our project, run tests and if all tests fail then package and publish to TeamCity's feed to Octopus to detect.
This isn't to big of an issue because TeamCity won't automatically deploy as it stands now. However if a user logs into Octopus and manually creates a release, they can select the potentially broken artifacts.
3 votes -
Deploy Nuget package to Nuget Feed
I want to be able to deploy Nuget packages to a Nuget Feed directly from the Octopus Server - I dont want to have to publish to a server that has a tentacle on it then run a script to deploy the package.
8 votes -
Add setting to project to indicate that the packages should all be the same version
Our project deploys multiple packages and always uses the same version across all the packages per release. It would be nice to have a setting at the project-level to indicate this. This setting could allow the user to select the version once when creating a release and help prevent the user from accidentally entering a different version for one of the packages.
1 vote -
List variable names from .config and .ps1
If octopus could scan packages for variables from Web.config, app.config and xxxDeploy.ps1, looking for appsettings and connectionstrings and $OctopusParameters[]. Then when adding variables it could suggest variable names. But also when creating a release it could warn about new settings/variables that have been added since last release and for which there was no variable?
Maybe it would actually be octopack that scanned for variable names and provided it as metadata in the nuget spec?
1 vote -
Support a restart as part of a deployment
One of my deployments installs an MSI that can require a restart. At the moment I have it failing the deployment if the error code from the installer indicates a restart is required. When the deployment fails, I manually restart the machine, then restart the deployment manually. Ideally it would be nice if I could ask Octopus to restart and resume the deployment from within the powershell script. I can pull the MSI out into its own NuGet pkg but I'm still left with being unable to restart the machine and resume the deployment as part of the Octopus deployment…
40 votes -
Re-evaluate variables containing nested variables set from Powershell scripts
Currently, if you have a variable containing other nested variables, and you set the value of the nested variable from a powershell script using Set-OctopusVariable, the value of the containing variable will not be modified.
If you want a web.config appsetting, for example called SiteUrl to be set, you would have to set the SiteUrl variable directly in the Powershell PreDeploy.ps1 script.
You could not, for example have a SiteUrl variables defined in Octopus as #{SiteHost}/#{SitePath} and then set SiteHost or SitePath in a Powershell script using Set-OctopusVariable.
Firstly, it is not particularly dicoverable that this is happening.
Secondly, it…
7 votes -
Set Variables from octo.exe create-release
It would be useful to be able to set the value of octopus variables as part of the octo.exe create-release command.
In our case, we would like to use some values from the build server in our web configuration (branch name). We are currently able to work around this by including the branch name in the package name (we could alternatively write it to a text file in the package), parsing it out using a regex and setting an octopus variable using a powershell script but it it cumbersome and fragile. Additionally, variables set from powershell scripts cannot be used…
11 votes -
Store XML transformations in Octopus
It would be more convenient to store XML transformation files in octopus project's configuration, not in source code hence it:
- pollutes source code
- pollutes destination folder
- divides configuration info as configuration info is stored in several places instead of one.
14 votes -
When creating a new release, default the Releases Notes from all of the checkin comments since the last release.
When creating a new release the Release Notes field is empty.
The way that we use Octopus, when someone is making a Release it is their job to manually copy across all the checkin comments (from Team City) for all the build versions since the last Release was made.
One per bullet (using markdown) so we get a nice list.Sometimes a checkin comment doesn't need to go in the release notes, or it needs to be elaborated, ... no worries. That is part of the manual job.
So what this idea is about is: how wonderful it would be…
11 votes -
Add CCTray Support to monitor deploys from the CCTray tool
CCtray the Cruise Control.Net Notfication Tray tool is a tool that polls a well known xml format and displays notifications on success or failure of builds. Team City now supports this format out of the box, and deployments in octopus actually follow a similar state pattern, where you could notify of a deployment by environment that is currently running, and report on the result of the deployment as success or failed.
5 votes
- Don't see your idea?