Currently you can throttle the number of package aquisitions and the number of machines which will run steps in parallel.
We see issues whereby too many steps run on the same machine causing out of memory issues.
Can you please add configuration to limit the number of steps running in parallel on a single machine12 votes
Good news – we’ve started planning this work over here: https://github.com/OctopusDeploy/Issues/issues/3305 :)
User interface shows hours and minutes, however the API is returning a time span of days, so for example I've set 99 hours, but the time span from the API is 2376 hours or 99 days.16 votes
This has been confirmed as a bug so has been moved to GitHub. Thanks for the report. Please reach us on our support channels to inquire or report bugs like this :)
It would be nice to hide the "un-tenanted" group of releases shown on the dashboard and project overview, if the project is configured as "require a tenant for all deployments". We don't want to delete these old releases, but they are no longer relevant to us and interfer with the information shown on the dashboard.10 votes
See https://github.com/OctopusDeploy/Issues/issues/3169 for our plan and a workaround to get you started right now!
Provide some really good guidance to help people use TFS and Octopus together.114 votes
We’ll be building this very soon
Potentially create some kind of SDK to allow for hooking into various parts of Octopus. e.g.: permissions/users could be given a custom implementation and provided by active directory.
Example plugins we should build:59 votes
We’re going to start on this very soon. I’d love to collect more examples of what people want to do with plugins (not so much how the plugin would work/what kind of extensibility, but the actual problem you want to solve)
- Don't see your idea?