1457 results found
-
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 -
Prioritize Deployments
Allow for prioritizing deployments by environment, project, or manually for a specific release.
We have 4 environments (Development, QA, Training, and Production) and would like to prioritize Production deployments higher than any other environment. Without this feature we sometimes have several deployments going to Development that slow down or force a Production deployment to be in the queue.
We also have specific projects that, if deployed, we would always want to take precedence over any other deployment regardless of environment.
50 votes -
Allow Windows Service feature to Grant user access to service on remote machine
To get around concerns for security, one option would be to have checkbox (default unchecked) that would be displayed when choosing Custom User that would say something along the lines of "Grant logon as a service rights if new user". Therefore it's still up to the user to decide whether it's needed or not.
Source: http://help.octopusdeploy.com/discussions/problems/21919
50 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 for importing and exporting of variables in a project or set
Allow for importing of variables in a project or library set in XLS or similar format. This way it can be edited, sorted, managed outside the Octopus UI then imported back in. This will also allow for a copy of a projects variables for reuse, instead of having to clone
45 votes -
Edit ordering of Library variable sets.
We should have an option to reorder the library variable sets. This will be very helpful when a large number of Library variable sets are used and need to be organised.
Source: http://help.octopusdeploy.com/discussions/questions/10415
44 votes -
Allow output variables to be referenced by ID and not (just) step name
Currently the way to reference a variable that was created from another step (an output variable) is by putting the step name between quared brackets like this:
$OctopusParameters["Octopus.Action[Step Name].Output.VariableName"]
{Octopus.Action[Step NAme].Output.VariableName}
The problem is that the step name might change, rendering this syntax useless. Same thing if we'd use step # instead (what if the step gets moved?).
The logical thing would be to use an immutable property like a step ID (Steps-1). The problem is that we currently do not have such ID for steps, as we reference them with GUIDs which are not human-friendly, and adding them would…
44 votes -
Fail the deploy if any missing variable substitutions are detected (unless overridden some legacy variable support)
We use web.config transforms extensively but from time to time will missing scoping an Octopus variable so the resulting variable substitution does not happen and we are left with #{SomeMissingVariable) in web.config. The results in YSOD errors at runtime. It would be very helpful if Octopus would fail the deploy when it detected un-substituted variables in final web.config (similar to how Ocotpus now fails the deploy when a transform warning occurs).
44 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 -
Add support for searching Octopus user defined variables
We have many user defined variables (some at the project level, some in variable sets). It would be really nice, if Octopus had a variable search feature so we could search for variable "Foo%" and Octopus would show all the projects / variable sets where "Foo%" was defined and what the scoped values were.
43 votes -
Scoping library variables based on Project Group.
We have common variables used by all the projects in a project group. The only way to share them across the projects (currently) is to place these variables in the “Library Variables”. Unfortunately, it exposes these variables to everyone else and we really need it to be restricted to just the group.
42 votes -
Generate architecture diagrams
If you are using OD as your deployment strategy, it knows everything about how your applications are deployed (potentially what databases are being updated), and where they are being deployed to.
If would be super-useful to be able to export the view (at any given point) to generate an architecture diagram of all the systems.
This would help keep any documentation on location of services up-to-date as well as providing a simple overview of where things are.
40 votes -
Support a restart as part of a deployment
One of my deployments installs an MSI that can require a restart. At the moment I have it failing the deployment if the error code from the installer indicates a restart is required. When the deployment fails, I manually restart the machine, then restart the deployment manually. Ideally it would be nice if I could ask Octopus to restart and resume the deployment from within the powershell script. I can pull the MSI out into its own NuGet pkg but I'm still left with being unable to restart the machine and resume the deployment as part of the Octopus deployment…
40 votes -
Configure path package is deployed to
Hi,
I have set up Deployment process and everything works fine except one thing.
I cannot find a way to edit step "zero" - downloading and unpacking of deployment package (nuget package).
In our deployment we process multiple tenants on single environment.What Octopus currently does (this process seems automatic to me):
- Downloads correct package version if its not already downloaded (this is ok)
- Unpacks it into C:\Octopus\Applications\tenantName\Production\projectName\projectVersion (want to change this)
- Then uses this folder as source of data (ok).I have TWO problems with this approach:
1)
while deploying on multiple tenants after ONE deploy…39 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 -
Highlight the variable Snapshot difference while updating the release snapshot
Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done…
38 votes -
Add support for machine name to show in Deployment.SpecificMachines
The Octopus.Deployment.SpecificMachine names are fairly useless when it comes to reporting specifically within an email step.
I've an email step at the start of deployment that emails people that a deployment is about to happen. We currently have a very flaky machine that keeps dissapperaing off the network and whilst it is gone we are deploying only to the rest of the machines.
I'm trying to add the ability to indicate which machines a specific deployment is going to and I know the Octopus.Deployment.SpecificMachines variable exists but it only contains the octopus id of the machine(s) (e.g machine-12) rather than…38 votes -
Add an option to notify members of the responsible team on Manual Intervention Steps
When adding a manual intervention step (say for approval to deploy to production) It would be nice to have a checkbox on the step configuration that sends an email to all users of the "responsible teams" containing the instructions and a link to the release.
While we're on the subject, it would also be great to be able to set a Team as an addressee on the the Send Email step template.
38 votes -
Add Let's Encrypt support to the Certificates Library functionality
I love the Let's Encrypt integration with the OD server. Setting up SSL for the server is so simple, and I don't even have to worry about renewals as this is taken care of for me.
Now imagine this same functionality for all of your IIS sites.
This is how I envision it could work
- I go to Library > Certificates > Add certificate
- I'm given the option of importing a cert (i.e. the current functionality), or I can chose to use Let's Encrypt
- After picking Let's Encrypt, I'm prompted for a bit of info- domain, email address, verification process…
36 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