522 results found
-
Compound Step Templates
This feature seems to be used internally by Octopus Deploy and can be seen in the "Deploy an IIS Web Site" step template created by Octopus Deploy.
When I add the "Deploy an IIS Web Site" step template created by Octopus Deploy to a project process I am presented with 3 options under the "IIS Deployment Type". As I select the different radio buttons the actual step template parameters that the user is able to fill out changes.
For example, when I switch from the "IIS Web Site" option to the "IIS Web Application" option, the very next section changes…
1 vote -
Show tags to the tenanted project page
It would be nice to see the tags that are assigned to the tenant on the project page .
1 vote -
Configure Azure App Service deployment parallelism
We encountered an issue recently where a large number of deployments were launched to Web App which are all using the same Azure App Service.
This resulted in high CPU usage on the App Service and deployments started failing and terminating with errors connecting to the /msdeploy.axd endpoint of the Web App. Additionally the Web Apps themselves became unresponsive and we had to stop all Web Apps and start them one by one and then re-launch deployments in series to resolve.
A simple workaround is to ask users not to launch too many deployments at once, but it would be…
1 vote -
Soft "lock" on variables
We recently had an admin accidentally change the wrong variable in a deployment because they were not paying attention. In this particular instance it was important since it was a connection string. Since variables with the same name appear on top of each other if they are scoped differently, he thought he was chose the variable for the incorrect environment. I understand this will be helped a bit with the new UI, but a variable "lock", something like a confirmation checkbox that you would then have check to "unlock" or some simple mechanism that would prevent someone from inadvertently changing…
1 vote -
Environment panel in Deployment screen should be Tenant-aware
The little Environment panel shown at the bottom-right-hand-side of the Deployment screen shows "other Deployments of this Project". However, when implementing a tenanted Project, this panel shows deployments to all Tenants instead of "other Deployments of this Project for this Tenant".
Each Deployment has a TenantId which could be used to further filter this panel and make it more useful for tenanted projects.
1 vote -
Allow releases to be pinned
I would like to propose the ability to pin a release.
This would exclude the release from the retention policies and the release could only be deleted manually.We deliver new releases with either a "-stable" or "-dev" suffix and want to pin all "-stable" releases to not be deleted if we create new "-dev" releases.
The only solution would be to create an intermediate deployment target between "CI" and "Test" with a different retention policy as our customer decides when which version goes into Testing and finally into Production.
1 vote -
Support complex multi-package steps
I have a three-tier deployment with the addition of multiple services. It is incredibly complicated to have the services deployment step that consists of 20 unique packages. They are independent and can be deployed to multiple servers. I just want a way to easily handle them from the admin/UI side as a single entity even though they are made up of the multiple packages. This is a real user experience/maintenance blocker for us.
1 vote -
version
We've begun configuring Octopus, however, we want to leverage S3 as the storage of our artifacts. There is currently nothing native to support this, so we've had to use scripts to do the file copying. We are now at the point where we need to handle the version number we're deploying. How can we dynamically generate this version?
I'd like to be able to execute a script during the first deployment to get the version from anywhere. (ie: AssemblyInfo details, or even opening a file and reading the version from it.)
1 vote -
Add the ability to skip steps based of the value of a prior steps output variable.
I would like the ability to set Octopus variables in a PowerShell script step and then conditionally run or skip later steps in the project based on one of the variables value.
1 vote -
Add more fields to date for version template
Currently we have following options for release version template:
"Octopus.Date.(Day|Month|Year|DayOfYear)"It would be helpful if we had bit more options in here. Such as
WeekOfYear
QuarterOfYear
DayOfQuarter...or if some math operations were available, so we can calculate the needed value.
1 vote -
Improve support for Canary deployments
Sometimes, willingly or not, we end up having our set of machines on different releases.
The following would improve the support in this scenario:
- An overview page for each Project that shows which machines are on which release
- When starting a deploy, the possibility to move all the machine to release A to release B (including the possibility to downgrade)
1 vote -
When creating a release ONLY return the builds that match the "Specific" search criteria. Or at least return the list sorted. It is a pain!
When creating a release ONLY return the builds that match the "Specific" search criteria. Or at least return the list sorted. It is a pain right now!
1 vote -
Show deployment targets (machines/servers) on task summary page
Hi,
I've been asked for a list of servers deployed to by one of my apps. To see the list I've had to go to the previous deployment and copy the machine names from the 'Acquire Packages' section as the environment could have changed since the deployment was done.
Therefore the solution to me is to display the list of targets/servers/machines used in a deployment task on the summary page of a task. As a task is generic I would think it'd have to be on the right hand side with the environment, history and artifacts section and maybe something…
1 vote -
Allow an option to run config trasfomations/variable substitution for steps, skipped due to same package version is already installed
It would be great if there was an option to allow "partially" skip the package installation due to same version. Allow to skip/run selectable features.
I have an application, that contains several parts - Database, Backend engine, Front-end UI and some services.
If only the database updated in the new release, all other packages are skipped. However, I need to update Backend config variables to a new database name.If I could skip the installation, but run the config transform/variable substitution, it would be much cleaner, comparing to what I am doing now.
1 vote -
A better way to update AzureRM Powershell module
We ran into an issue today where one of the powershell commandlets included in latest version of AzureRm powershell module was not available on OD server and we had to manually install/update that version, then got surprised the updated version was not used because Octopus includes an internal/embedded version of the module.
I wish there is a better way to install and update AzureRM powershell module rather than wait for Octopus Deploy upgrades to refresh them.
Or maybe a way to choose when installing to use embedded version or other shared version pre-installed on the system.
1 vote -
Separate permission for editing variable values without edit on the variables themselves
Creating the variables is often the job of a developer since they are familiar with which variables need to be replaced.
But setting the variable value (ie a database password for the production environment) is typically the duty from an infrastructure/sysops person.
However, a developer doesn't necessarily want somebody from sysops adding or removing variables. Sysops should ONLY be able to edit the value of a variable.
1 vote -
Allow to enter tags for channel steps when creating release
Instead of changing tags in the Channels, they could have default values and whenever you create new release and pick the channel from the dropdown you could change the tags in the popup. It would allow multiple teams working on different branches to use the same channels without altering them.
1 vote -
Collapse All option on Deployment Task Log
I frequently need to collapse the details for numerous steps on the deployment Task Log. This is particularly important to do when wanting to switch to Verbose output. Failing to collapse all of the items, except for a particular step, results in a massive amount of information being displayed and thus making it difficult to find a specific section within the step of particular interest.
1 vote -
Make the bullhorn only visible via role
I'm wondering if it is a good idea to have the update bullhorn icon / link visible based on role. As it is now, the bullhorn pops up whether you can update Octopus Deploy or not. If you turn off the update notification, you will not get the update notification at all, even as an administrator.
It doesn't make sense that normal users are reminded about updates if they cannot do an upgrade.
1 vote -
Provide the ability to define a Release Notes template
Someone suggested providing an Octopus Deploy "built-in" variable for storing release notes (see here).
While this is a good idea, I feel it would be even better to just be able to define a template for release notes, which itself can contain other variables and/or be populated by a variable or script or whatnot (imagine, running something like git-release-pull to "auto-generate" your release notes based off of merge commits to master, for example).
In my case, I'd like to be able to prompt for a TFS Build URL and the web server URL for accessing the newly deployed release.…
1 vote