1458 results found
-
Reorder variables on Project Variables Screen
On a projects Variables screen, once we enter a new variable it stays in order on the screen. I would like the ability to drag and drop each line to a new position. This way I can ensure as I add new vars or update existing ones the ordering of them makes sense (at least to me)
22 votes -
Allow prompt variables to be scoped to more than just environments
As of 3.0.11. prompt variables can only be scoped to environments. It would be good to be able to scope them to steps, roles and machines as well.
22 votes -
Add function to OctoPack to 'clean' old nuget packages from bin
Adding a 'clean' function (similar in nature to MSBuild clean) that removes old packages when creating the new one. Especially relevant for when you publish the package to a file share or feed.
22 votes -
Advanced Tentacle cleanup for deleted Octopus items
Currently retention policies will only run on a Tentacle during a deployment and only for the project currently deploying. There are cases where you delete a project, channel or tenant meaning even if a deployment is run on the Tentacle those previous releases will never be deleted.
The idea being raises will give the ability for a cleanup process to be run on an environment for all active machines. It will compare existing projects, tenants (etc where relevant) against the deployment journal and if there are records in the deployment journal that cannot be matched to the triggering instance those…
21 votes -
Make sensitive variables more secure
Sensitive variables pass to script as a String, so they could be written to file/socket. I think there should be an option to make those variables more secure and pass them as SecureString instead of String.
21 votes -
Cloud Foundry Support (Pivotal)
We've started looking into handling container deployments with Pivotal Web Services, it'd be great to add Cloud Foundry support as a deployment option, similar to AWS or Azure.
21 votes -
Save Step Templates as Powershell instead of JSON
The current JSON style templates makes it somewhat difficult to manage updates and changes. When comparing a template exported from my Octopus server against one from the community library (or GitHub), most of the metadata properties are the same and aren't interesting. What's more interesting is comparing the actual Powershell script changes. But having the script embedded in a single line of JSON makes it extremely difficult to actually make a comparison to see what really changed.
Furthermore, in our organization, when we want to make a change for a template in our GitHub branch, pull requests are difficult for…
21 votes -
Undeploy project from servers
We miss ability to undeploy a project from servers.
Undeployment could run an Undeploy.ps1 script from the package that would contain logic for removing the service from a server (removing web app files, deleting databases, uninstalling a software).
Currently there is no way to remove a project from a server if it is no longer used to run a service from the project (eg. changing where an web app will run, or removing programs installed by the deployment scripts).
21 votes -
Implement SFTP Support in the FTP Package Deployment Step Template
The FTP deployment step supports FTP and FTPS but not SFTP. Adding this would let Octopus users securely deploy to a much broader range of systems (i.e. Unix-y ones instead of Windows).
21 votes -
Configuration variables support for SMTP settings
It would be great if Octopus would replace values in the smtp (http://msdn.microsoft.com/en-us/library/ms164240(v=vs.110).aspx) element in web.config like it does with connectionStrings and appSettings.
21 votes -
Support for app settings from Application Pool in IIS
We currently want to set features like the number of worker processes. It would be good to be able to set these up from Octopus instead of powershell.
21 votes -
Run uninstall on the currently deployed solution
We've just moved our service over to use TopShelf. Previously it used its own installer. In PostDeploy.ps1 we woudl then run installutil with teh service as an argument to install the services and message queues.
Now we don't need the installer inside the service anymore because TopShelf does that for us.
The problem is then how to get the deployment to uninstall the service successfully when it has no cencept of uninstalling the currently deployed installation using the artifacts of that deployed installation.
I have to try to uninstall the previous deployment using the new deployment artifacts. This is causing…
21 votes -
Integrate Octopus with ServiceNow Change Management
Native integration with ServiceNow so teams can link releases to change requests and pause deployments to production until approvals are met.
20 votesWe are working on an ServiceNow integration, focused on connecting deployments and change requests. You can sign up for updates from the product team on our Roadmap page.
-
Add cmdlet to download artifact
New-OctopusArtifact allows you to attach an artifact to a release. If you wanted to use that same artifact in another step on the same deployment, you'd need to use the API.
It might not be such a bad idea to have a
Get-OctopusArtifactcmdlet that returns info about that artifact, as well as aDownload()method the download the full file from a Tentacle.20 votes -
AWS Elastic Beanstalk support
Fully support of Elastic Beanstalk for deploying HA web applications that make use of the built in feature set plus the rich features provided. H octopus.
20 votes -
Collect logs from offline installs
Offline install packages are a nice way of introducing Octopus and Calimari installs into an existing enterprise without having to directly attempt to change the change management process straight off.
However in doing so one of the principal 'sell' points of Octopus - centralized logging - is lost.
It would be nice if offline installation also took care of transmitting the installation logs back to the central server (presumably if possible), so the installs would look largely like any other install.
20 votes -
Skip to failed step on "Try Again"
When choosing to try again on a deployment it would be really nice to have an option to skip all steps that did deploy successfully.
20 votes -
Use Script Modules in Script Console
Title describes the idea pretty well.
Source: http://help.octopusdeploy.com/discussions/questions/9451
19 votes -
Moved recetly deleted projects into a "trash" location so can easily restore them
I have accidentally deleted projects multiple times now.
When I am in a rush and want to manually recreate a release I have to delete it - which has a very similar sequence of actions required to delete the project! :(
The only way to get the project back is to restore the database. It would be nice if you could just hide the project from the GUI and keep it into a trash can somewhere which could retain it for a limited perioud (e.g. a month).19 votes -
Make steps collapsable when they contain child steps
When working with larger projects that contain steps within steps, the page refreshes often when making changes so this involves a lot of scrolling to find the steps you are working on. It would be great if you could collapse steps that contain children so there's a smaller list to scroll through.
19 votes
