314 results found
-
Preview Transforms for an Environment
When updating Variables, it would be great to see what Octopus will change the web.config to when deployed to an environment without actually deploying it.
57 votes -
Manually force retention policies on tentacles
Currently, retention policies are applied at the end of a deployment only. It might be good to have a way to force retention policies on tentacles outside of the context of a deployment. Maybe a button on Configuration -> Retention -> Top right corner, specific for tentacles.
53 votes -
Allow cloning Library Variable Sets
Allow cloning of library variable sets so it becomes easier to create a new variable set for a new environment.
51 votes -
Ability to disable some standard step templates
We want to standardize on some templates that all developers can use for their deployments. That because we need to add compliance checks on all code before promoting to Production.
the 'Run custom script' built-in step is dangerous because that opens the opportunity to do more or less anything.As an Octopus admin I want to disable some of the built in step templates.
47 votes -
Allow login only to users in specific AD groups (white list)
Any user that knows the Octopus portal URL can log into Octopus, which will create them a user on the Octopus DB and add them to the "Everyone" group, create entries on the Audit log, etc.
Even though the user won't have any privileges out of the box, implementing a white list system to only allow people in specific AD groups to login would be something good.
43 votes -
Change Polling Times
From what I can see, there is no way to change the Polling times for Tentacle clients. The default is every 5 seconds.
It would be good if we can configure this on an individual Tentacle basis and change the interval (maybe through the environment page).
Due to our setup we can only use the Polling technique.
This is our scenario:
We have around 100 web servers spread across 3 environments, DEV, UAT & Production. We have configured this to go through a FW. As an outcome we are flooding our logs with trivial data on the FW.
As we…
39 votes -
Allow custom dashboards
Some of our ops need different dashboard views depending on what they are interested in at the time ... would be could to be able to save 'named' dashboard views that you can easily change in a drop down menu or something similar.
36 votes -
Support the archiving of non-active projects
From the following support topic http://help.octopusdeploy.com/discussions/questions/6809-archiving-projects
Octopus deploy does not currently support a model for archiving/unarchiving non-active or legacy projects.
The workarounds are permission-based or user-specific but not quite what I would like to see.
what I am suggesting is similar to Teamcity's archiving functionality. I have found this ability in TC to be useful in the 7+ years I have been using it where I have accumulated many different applications, some of which are no-longer in production, some which are in production but in maintenance mode only and those in active ongoing development.
For the most part I only…
35 votes -
Add the ability to delete releases and deployments from the dashboard
Currently the only way for a release to be deleted from Octopus Deploy is using the retention policies. I think it would be a good idea to allow administrators to delete releases from within the octopus dash board. The administrator should have the following options:
- Bulk removal of releases - This would be similar to the retention policies. Remove all but the last X releases\deployments
- The ability to remove a single release. Selecting the release should now give the administrator the ability to remove the release
- Administrator should also have the ability to remove deployments as well.
- This should be…
35 votes -
Set tenant "Common Variables" per environment
As of Octopus 2018.2.3, I'm experiencing a limitation for defining variables per tenant and environment.
The current ability to define variable templates per project is nice (so we can change the value per environment as the project is deployed to those environments). However, it would be nice to have the ability to define a common variable template that is shared across all projects in the deployment per tenant, but can change per environment.
I understand this can easily be done via variable sets, but it would be nice to be able to define everything in one place--not simply dividing configured…
32 votes -
audit search
Please add search functionality to the audit log. The filtering helps but trying to find changes to a variable library for example is nearly impossible.
23 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 -
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 -
SSL Certificate Expiry notification with X Number of days
It would be great to be able to set the number of days for which a Notifcation of an SSL certificate takes place.
Due to a number of external factors we normally plan SSL replacements 60 days in advance so the 20 day expiry warning that is currently set will not be viable.
17 votes -
Allow for teams to be excluded access to environments, not just included
Currently in the Teams area you can either allow team access to All Environments or select which environments they have access to by including them explicitly. It would be great if we could select environments they should be excluded from (UAT, Production, etc).
We're trying to take advantages of Azure and the ability to create test environments on the fly that allow our testers and developers to create environments for them to deploy to. Under the current access rules they need the ability to access all environments (leaving the Environments access field blank) or add each environment as it is…
17 votes -
Connect project to many tenants at once
There is currently no way to associate a project to multiple tenants without going into each tenant one by one, finding the project, selecting an environment, and clicking Save. For installations with many (tens or more) tenants, this is quite inconvenient, and has resulted in hacky workarounds from third-parties.
16 votes -
Marking a release amongst release candidates
It should be possible to mark/tag a specific release.
The reason is that we are building a lot of release candidates, but only some of those actually forms a final release, that can be installed at our customers environment.
By marking/tagging these and highlight them in the GUI, it is possible for people to see if an official release is installed at an environment or not.
This should always be the case in production, and it would be nice to quickly have an overview of that is the case or not.See also this discussion:
http://help.octopusdeploy.com/discussions/questions/8125-marking-a-release-amongst-release-candidates14 votes -
Support for MySQL and other RDBMS
Support vor databases other than SQL Server.
14 votes -
Octopus Reporting Feature in built in the Octopus Tool.
Octopus tool to generate Report based on
1. What's Deployed ?
2. Who Deployed ?
3. Deployed To Where ?
4. Who Approved ? (Manual Intervention Step)
5. When did the deployment Take place (Week Day & Weekend deployments)14 votes -
Create jobs for recurring tasks. Use permissions to control task jobs by environment.
Create task jobs for recurring tasks. Use permissions to control task jobs by environment, project, node.
The QA Team could be assigned permissions on a task job to run an iisreset on all servers in the QA environment or particular projects in the environment. Dev Leads could restart Windows services on individual nodes in Dev. Right now a user has to be an Octopus admin to run a custom shell script but we don't want the Dev teams to be able to affect production. I'd rather just create a task job so Dev or QA does not mistakenly run the…
12 votes