314 results found
-
Allow for expiration of users in a team
We have a need to setup a Production Release Day Only team, and right now we add users to that on production release day, and then have to remember to remove those users, because we don't want them to have access to production forever. It would be nice if a team could be created that has a configurable number of days where any users in that team that have been in that team for more than that configuration would automatically be deleted from the team.
1 vote -
Group scripts in the Octopus Deploy Library by Category
As the number of scripts in the library grows it will be helpful to add more structure to it using categories and/or tags.
Add a "category" and "tag" field to the metadata for each script in the Octopus Deploy Library.
Change the UI to group scripts by Category.
Initial categories could include:-
Workflow (Wait, ...)
Windows
NT Service
IIS
Database
Test (NUnit, Http request, ...)
Data Collection (Disk space, CPU, ...)
Integrations (Slack, Hipchat, ...)
Network Environment (Load Balancers, CDNs, etc.)1 vote -
User description
Something I would like to see is user description. We have a few service users and since there is no description we are using a mix of display name and a page in confluence to describe their roles and scope.
And what about having a place to store API keys? Only available to certain roles, let's say system administrators.
1 vote -
Multiple Component Projects
Often times various components that make up a 'whole' project can exist at different version numbers. A WebApi project perhaps, a UI project, a SQL Database project. The three of these things together comprise a single solution. It would be nice to have component based projects (as currently implemented) and then to have a sort of parent/solution container.. so that for the container, I can click a button and bam, all sub-projects get deployed.. or, if I want, I just click a button and release individual pieces of that whole project.
3 votes -
Use a web resource as a proxy for a listening tentacle
I'm working in an environment where web servers are sitting in a DMZ that only allows incoming HTTP traffic - no outgoing traffic at all is permitted without going through numerous administrative channels to get ports opened. I do however have full administrative access to the server only.
I could deploy a tentacle in this scenario if I had some kind of web resource that acted as a proxy for a listening tentacle. Octopus would manage the tentacle via <site>/octopus-deploy.axd instead of through the usual listen port.
1 vote -
Support PCI Compliance with a Single Octopus Server
What would be ideal is for Octopus Deploy to attain a "PCI-certified" status.
I don't know whether this would require 2 linked Octopus servers (as suggested elsewhere), or whether it could be accomplished with a single Octopus server. Here's one idea for the latter (it might display my ignorance)...
Switch Octopus into a new "PCI-compliant" mode.
Use a clever permissions strategy to segregate users into either:
- a ProductionDeployments role, or
- something else.
Certain target environments would be designated as Production.
Only those in the ProductionDeployments role would be allowed to promote a product version to a production environment. Everyone who…
3 votes -
Machine Roles: The ability to 'define/manage' these
Hi
I'm using Octopus but the one thing i find a potential problem with is the ability to arbitrarily assign a machine to any role i type in.
I would like to see the ability to have a 'machine' roles 'table' that needs to be setup before any machines can be added to a role.
That way, machine roles can be managed (CRUD functionality).
Thanks!
4 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 -
Restrict a machine to only specific enviroment
I am an administrator and I manage 3 environments DEV/QA/PROD. After I install Tentacle in a prod server, I should be able to add that machine only under production environment.
One way to do is by having a different thumbprint for each of the environments.
6 votes -
Provide visual indication when step feature is removed but configuration remains
Disabling a feature from a step should either remove the configuration (clear out the fields) or provide a visual queue that there is configuration that that will affect the step that is not visible.
I had a step performing an xml transformation. I removed the transformation feature, created a release and deployed but the transformation still occurred. I had to re-add the feature and clear the transformation fields to stop the step from performing it.
1 vote -
Add a simple cache to the NuGet respotories
Unfortunately, I am forced to work with a very slow NuGet feed and the more packages I upload the slower Octopus is at retrieving them when creating a deploy. Fixing the speed of this is out of my control.
It would be great if you could do some very simple caching to speed this up. Or can you simply limit the number of versions you get from the feed?
Anything to speed up this up would be fantastic.
2 votes -
Tracking releases on other octopus deploy servers
We have a host that controls UAT and production. They manually promote sites by hand currently but are open to something automated that they control.
Internally we have a CI environment and test server but don't want to give access to the host to our intranet or active directory or expose our octopus deploy to the host.
We would like to see the state of releases in UAT and production on the same board as our CI release.
1 vote -
Show default application directory in tentacle manager
On the tentacle manager screen, we currently see the 'Home directory' and 'Logs directory'. How about also showing the default 'Application directory' to which the tentacle deploys?
1 vote -
dashboard hover environment shows info of what servers it contains
on the dashboard, if you hover a deploy, you will get more information on that deploy in a little info-box. We would like to see the same behaviour but for the environments. If you hover "dev" it will list you what servers it contains, and a little icon for if it's up and running or disabled/not healthy)
1 vote -
Add Reporting
My Manager is demanding some reports. I would like to have something to give him.
5 votes -
Ability to bulk enable/disable all PCs in an environment
It will be really helpful to be able to enable/disable PC/Tentacle environment wide.
1 vote -
Scoping Variables to Only UI or Config files
I just set up a project where I created a variable called logfiles to use as a variable in a step template. I did that, and around the same time was looking at the documentation for how to do key/value pairs for web.config and I realized that I don't see a way to scope a variable to just configuration files or just the UI (or more intentionally NOT config files). My concern is that I will set a variable that ends up being a key in one of the config files and so I unintentionally update a value in the…
1 vote -
Queue Viewer
We've had a couple issues where something in the Queue froze and stopped all future deployments. When it's a project that seizes up, we can cancel it, however when it is an internal task (e.g. Tentacle Health Check), the only way to fix the issue is go into Raven Studio. I know I can see the completed tasks, but I would like to be able to view the queue, and perhaps cancel jobs from there as well.
1 vote -
Have a textarea for "notes" when promoting a release to an environemnt
In our setup, TeamCity creates and deploys a package to the "Test" environment. Then upon approval, a specific package will be promoted (by a human) to higher level environments (i.e. QA and Prod).
We need to write notes when doing so. i.e. Who approved it, etc.
4 votes -
Batch add or remove roles to servers
Adding or removing roles from clusters of servers that are 30+ servers is a pain to do one by one. it simply takes forever.
It would be fantastic if I could mark all the servers that I need to manipulate roles on have one dialog box open. Add and/or remove the roles I need to change. When pressing OK my job is done: I've successfully added the 'awesome' role to 30 servers in less than 1 minutes.
Also this would make my management work less error prone as today I might have missed a server or two in the process.
3 votes