315 results found
-
Highlight incomplete lifecycle
When managing a large number of applications and a series of environments, it can become difficult to tell at a glance from the dashboard when, for example, there is a version in QA or UAT that is awaiting promotion to a higher environment.
I would suggest adding the option to highligh releases that have not completed their lifecycle.
2 votes -
Option to add Tenants in the Project Settings
As a project Admin, we don't have access to add the Project to different Tenants. Instead can you add an option in the Project settings to add required Tenants for that Project?
Regards,
Manasa Bhavanari2 votes -
Share project group and environment security between teams
I've started to accumulate lots of environments and project groups as well as having lots of teams.
Most of the teams have access to the same project group and environments, however the teams will have different roles. As it is now, creating a new project group / environment means having to update all the related teams manually. This procedure is prone to errors.
Why not create something similar to life cycles? But instead of describing the direction of deployment, the security setting describes project group and environment access.
F.ex:
Security View 1 contains access to
4 project groups and 3…1 vote -
Dashbaord UI Tweaks - Give search box focus by default & by CTRL+F
Hi
A couple of UI tweaks on the dashboard would be great when dealing with lots of projects:Give search box focus by default
Give search box focus when pressing CTRL+F2 votes -
HA Active Task Handoff Between Nodes (for Drain)
Currently I believe that "drain" on HA clusters simply waits for tasks to finish. This is okay when we are draining during scheduled downtime / low deployment time.
However, as CI and automation mean deployments are happening constantly this creates a few issues.
Scenario 1: Hard reboots need to wait for a full drain - We had a rogue deployment spitting out 200k lines of text on a HA node effectively bringing it to its knees. Even task cancellation was failing due to all the excessive buffering. Hard resetting the node is a problem with active tasks.
This scenario also…
1 vote -
Within teams, allow us to scope different roles
My organization has several developers across different teams. I have a "Base Developer" role assigned to a single team with every single developer in that team which gives them most of their permissions, scoped to all projects and all environments. This role does NOT include ProjectView or DeployCreate permissions.
I have secondary teams for each "Group" with a Developer View/Deploy Role, where I can scope out which project groups they can see and which environments they can deploy to (DEV, QAT, UAT). The Base Developer role applies its permissions across "All Projects" but they can only see projects I've specified…
2 votes -
Add badge or small text area on the Dashboard that can be customized for each deployment
The Dashboard would have a badge or small text area next to each deployment that can be dynamically set. This value would display around the status icon and release number, and it could display the value of an Octopus variable that is set during the execution of a deployment step.
On the Dashboard, we want to show the number of successful integration tests from the NUnit step. However, I'm sure there would be other great uses if we had a text area of 20-50 characters that could provide a status that's more detailed than just Passed/Failed/Cancelled for the overall deployment.
1 vote -
Make it possible to have optional project variables
When adding a project variable, there could be a setting to make it optional. It would then be possible to leave it empty for any project/tenant using the variable.
2 votes -
Scheduled Downtime
Over the course of the year we have things like product demo's or even black out periods for holiday periods etc.
If we can have a calendar / schedule that can be set in advance to prevent changes in versions to be deployed, but still allow auto deploy to work. That would be very awesome.
1 vote -
Have an optional project learn mode - for added / new environment environments
What would be really cool is a feature where one can setup a project with all the steps for all environments knowing that for some the features will fail or are unnecessary but when you run in "project learn mode" the project learns from your responses and automatically updates the inclusions or exclusions for that environment. i.e. in project learn mode for a new or added environment you could choose to go into learn mode and are asked step by step as it runs if you want to apply the step to this environment and the systems remembers the response.
1 vote -
Add a visual indicator that a save is about to happen
When I edit e.g. a library variable set on our (admittedly underspecced) Octopus server, it takes a while before the set starts reloading with the changes. During that time, there's no visual indicator that my click action was registered.
If I look at the network traffic in devtools, I see:
- Click
- A few network requests, starting with a POST to the library set api.
- The UI starts updating, removing the list and adding a spinner
- More network traffic...
- The list reloads
It would be nice if what now happens at 3. could be moved before 2., to immediately visually indicate…
1 vote -
"Raw Octopus" for Windows Hosts
I read the post a few weeks ago about the "Raw" Octopus setup using SSH for Linux, I thought that to be an outstanding idea. Is it possible to be able to do the same thing with Windows without using an agent, like using WSMan or PSsessions or something? That would be fantastic!
1 vote -
db table index in azure
Azure suggested I should add a table index, that would have "high impact":
Table:[Deployment]
Indexed columns:[EnvironmentId], [ProjectId], [ReleaseId]I got about 4k rows in this table, and the octopus db is about 150mb. Using standard performance tier in azure, i.e. managed sql server, no custom vm.
Currently using octopus 3.11.4, but have upgraded the installation several times.
1 vote -
Add a reason textbox when checking disable on a deployment target
Add a simple reason/comment textbox when checking disable on a deployment target. This is for other team members to know why a target has been disabled.
Other info added cane be user signature and a datetime value.
If the deployment target is disabled by someone i expect something like:
[X] Disabled
Target was disabled by John DoeJohn.Doe@thecompany.com 12 may 2016: "The machine is at repair ticket #1234 - please enable when back".1 vote -
Provide SHA256 sums for downloads not just MD5
Downloads posted to https://octopus.com/downloads have MD5 sums available, but some tools use SHA256 to verfify downloads.
A specific example is discussed in this github issue: https://github.com/cvent/octopus-deploy-cookbook/issues/75
The workaround as mentioned is to download the binary, check the MD5 sum and then obtain the SHA256 sum on your own. While not difficult, it does introduce extra manual steps needed for each release.
Having access to Octopus provided SHA256 sum for each download would streamline the use of other automation tools like Chef to setup Octopus.
4 votes -
Display the health status of the environment in the dashboard
Rather than just having the name of the environment at the top of the dashboard, have an icon showing the health status (Red, Yellow, Green) as well
1 vote -
Please put the "Configure Dashboard" Included/Excluded lists in alphabetical order
My organisation has lots of projects, and I'm constantly having to re-configure my dashboard depending on what I need to do. Having these lists not in alphabetical order is very frustrating.
4 votes -
Explicitly support reverse proxies
While it should be possible to configure nginx/haproxy/etc to act as a transparent reverse proxy, it is a commonly accepted convention to use the
X-Forwarded-HostandX-Forwarded-Prototo pass the original requested url to the proxied application.It would be nice to support these headers.
3 votes -
Collapse channels by default
Channels should be collapsed by default. We do have just about 10 channels in one project, but they do contain lots of steps so we have to use Find on browser to be able to get to the channel we want.
1 vote -
User Management - Project Admin -Restrict the Admin User access to project, Environment specific.
When more than one project use the same instance, we should have an option to restrict admin role to project, environment specific.
That is admin of one project should only modify users of their own. It is like a project Admin.
Also Current Admin Role could be Super Admin and Project Administrators Can't Modify this.
1 vote