General
-
30 votes
This will be done in 2.5.3
-
IIS bindings configurable by environment
For a given project I often have one IIS binding for my staging environment:
project.testing.something
But the production servers have more
project.com
legacyprojectdomain.com
project.co.ukIt would be great to be able to configure this in a deployment step without having to have separate deployment steps for each environment
36 votesMarked as completed. These modifications have been available for a while. You can edit bindings once added and create a variable in ‘enabled’ scoped to environments so they will only be created/used for the environment being deployed too.
-
Enhance the "IIS web site and application pool" feature to support virtual directories
See http://help.octopusdeploy.com/discussions/problems/15298-how-can-i-deploy-an-iis-application-to-a-subpath-of-a-web-site. If this feature supported virtual directories, I could use it; but as it is, I must script all of these feature in Powershell.
57 votesStarting from Octopus 3.4.7 this feature is now supported by Octopus out of the box: https://octopus.com/blog/virtual-dir-iis-windows-service-steps
The library now contains a number of step templates for configuring IIS, including virtual directories and applications. I’ll do a blog post in the next few days about how to use them:
-
Add retention policies to internal NuGet server
Of course the NuGet server is easily managed manually through the file system, but it would be nice to have Octopus discard old packages based on some combination of date or last x versions.
33 votesDone! As of 2.4, packages in the internal feed are also deleted when the corresponding releases get deleted via retention policies.
-
Add filtering within audit log
The auditing feature is good, but without any filtering tools, it’s too cumbersome to navigate effectively. Can you add filtering options by: User, Date Range, project or team, action type, etc. etc.?
75 votesThanks for the suggestion everyone. I’ve implemented this in Octopus 2.3. Check out a screenshot here: https://github.com/OctopusDeploy/Issues/issues/701
-
Ability to "ignore" or "disable" a step
Make it possible to mark a step/action as "disabled" so that it does not get run.
Not sure what the scope should be - should it apply to any release with that step, or just new releases created?
3 votes -
Create a plugin for Atlassian Bamboo
Create a plugin that makes it easy to trigger a deployment in Octopus from Atlassian Bamboo, like the TeamCity plugin.
17 votesWe’ve added a documentation page about using Octopus with Bamboo – it seems like a full plugin isn’t really required just yet as making Bamboo call Octo.exe is very easy.
-
Show variables from included variable sets
You can re-use Variable Sets into multiple projects, which is great.
However when you go to visit your projects Variables page, it just says a Variable set is Included. You get no real information (or link) on which variables are included in that variable set.
It would provide a better overview if the Variables page also listed the variables in the Variable sets. (read-only)6 votesThis information was made available in the variable preview, released in 2018.3
-
regex to filter the nuget packages when creating a release
Any possibility of enabling us to specify a regex to filter the nuget packages when on screen after clicking "create release"?
We have multiple branches of the code being worked on at the same time. Each branch has a different major and or minor number.
Ideally we would like to be able to filter accordingly so that we see the latest matching a regular experssion or major / minor version.Source: http://help.octopusdeploy.com/discussions/questions/2474
1 voteThis feature is available as part of Package rules in Channels https://octopus.com/docs/deployment-process/channels#Channels-versionrules
-
Add grouping for variables list
We need a better view for the variables in a project, once you have a few variables it becomes difficult to make head or tail of the variables list. Particularly when you start to have variables with the same name but different values dependent on scope (i.e. environment)
We should be able to group the list by scope or name
39 votesAs of Octopus 4.0, the new variable screen performs grouping on variables with the same name.
-
Update documentation around artifacts
Please update the documentation around artifacts. It is very hard to find how they work.
I know there is a small part in here:
http://docs.octopusdeploy.com/display/OD/Script+Console#ScriptConsole-CollectingartifactsUpdate this page with details or a link to the Artifacts section:
http://docs.octopusdeploy.com/display/OD/PowerShell+scripts
This is where I'd need it most not in the script console which feels more of an ad-hoc type of running stuff on the servers.On the Task Summary page there is an "Artifacts" area (top-right). Add a link from there to the help page from 1 about what artifacts are and how can they be captured.
9 votesWe’ve updated the docs and the link in the deployment page will ship as part of the next patch to 3.3. Hope that helps!
-
Expand contents of NuGet packages
When viewing a NuGet package, it would be nice to expand and see what is inside it (perhaps just for the built-in repository or repositories on a file share):
9 votesYou can currently download a nuget package from “library/builtinrepository” and view packages as required.
-
Create a plugin for Jenkins
Create a plugin that makes it easy to trigger a deployment in Octopus from Jenkins, like the existing TeamCity plugin.
9 votesWe’ve added some documentation on using Octo.exe with Jenkins, and it’s very easy to do. We won’t be creating a full-blown plugin just yet.
-
Email notification of health check failure
It would be useful to be able to get an email notification if any of my machines fail a health check.
17 votesThis is now available as of 3.5 as part of our subscriptions feature.
https://octopus.com/docs/administration/subscriptions#Subscriptions-EmailNotifications outlines how subscriptions work and as you can see in https://octopus.com/docs/administration/subscription-events the “Machine found to be unhealthy” is one of the events that you are able to subscribe to. Happy deployments! -
Add a QA Role
In Octopus 2.0 security was greatly simplified into a set of canned roles.
A problem with these roles is that there is none that allow a user to only view releases and deploy to an environment. The existing "project deployer" role inherits from "project contributor" and automatically includes the ability to create and modify projects.
The use cases here is to allow QA & Test personnel to deploy a release to a testing environment, while ensuring they cannot modify project variables or the deployment process.
We've been successfully using this pattern with Octopus 1.6 to allow our testers full control…
25 votesIt is now possible to edit the built-in roles.
We’re going to make this possible, not by adding another built-in role, but by making it possible for you to add custom roles or modify the existing ones.
-
Reusable steps
We have some steps containing powershell scripts for e.g. deploying proxies, getting instances in and out of load balancers, running smoke tests etc. that are fully parameterized (relying on variables in the deploy project).
In order to keep it DRY it would be very useful to have a library of these step "templates" that could be referered from different deploy processes. Of course they would need different targets/roles, but other than that all that differs is the variables of the individual deploy projects.
2 votesCompleted in 2.4
-
Add per environment deploy process steps
Exact deploy steps required for each environment may be different.
I.e. steps for integration and staging may be:
- Clean machine
- Deploy new version
where as production may require you to perform some extra steps:
- Take a backup
- Clean Machine
- Install New Version
- Send Email to client
There are two simple ways of getting round this currently.
Add Production to the environment scoping for steps 1 and 4, this means they will only be run when deploying to production.
Or secondly using If conditions in the powershell to test which environment you are deploying to.
The problem with both of these…
27 votesWe added this quite some time ago
-
Allow for integrated AD authentication
Octopus 1.x allowed for integrated Active Directory authentication such that the user didn't have to logon again to access the website or even the api.
It would be very helpful to allow this to continue to occur in Octopus 2.0 as well so that the users don't have to continue to enter their credentials repeatedly.
Some corporate security policies do not allow for 'Remember Me' functionality to be used.
17 votes -
Use variable anywhere in configuration files
Right now, you can only replace values in a configuration if the variable name the name of an appsettings key OR the name of a connectionstringkey.
Why not let us put something like #{Server} ANYWHERE in the config file and have that replaced with a variable.
This would let us control things like
debug setting for compilation:debug="#{debugcompile}" targetFramework="4.5"
changing the 'subject text' for email config:
elmah xdt:Transform="Insert"><errorMail from="<a rel="nofollow noreferrer" href="mailto:somehere@somedomain.com">somehere@somedomain.com</a>" to="<a rel="nofollow noreferrer" href="mailto:errors@somedomain.com">errors@somedomain.com</a>" subject="#{Octopus.Machine.Name} - #{Octopus.Environment.Name} #{Octopus.Release.Number} " async="true"/>
</elmah>
We can do some of the above through transformations (debug setting), but we need a transformation…
18 votesThanks for the suggestion everyone. This will be implemented in Octopus 2.3 (I’m marking it “completed” because it is code complete although not released just yet).
You can view details here: http://octopusdeploy.com/blog/variable-substition-in-files
-
Make web site compatible with Android tablets
Would be nice if the the web site would work with my ASUS TF701T Android Jelly Bean tablet so that I can watch octopus videos and read documentation. The menus don't work on Android for some reason.
1 voteThe website has since been overhauled
- Don't see your idea?