Settings and activity
7 results found
-
60 votes
An error occurred while saving the comment -
60 votes
Josh Jones
supported this idea
·
-
28 votesJosh Jones
supported this idea
·
-
13 votesJosh Jones
supported this idea
·
-
1 vote
An error occurred while saving the comment Josh Jones
commented
Would the project ID not work for this situation? As far as I know it's unique.
#(Octopus.Project.Id)
https://octopus.com/docs/deployment-process/variables/system-variables -
55 votes
An error occurred while saving the comment Josh Jones
commented
Just the ability to control the "priority" within a queue would be nice from an Admin perspective (system team?). if there were 8 deployments queued and we had the ability to re-order any of the deployments in that queue (I would not expect to be able to "pause" a deployment in progress, but control the order of releases waiting to be deployed.)
Josh Jones
supported this idea
·
-
25 votesJosh Jones
supported this idea
·
I think this would be great, but I could see it being a bit of a pain to secure too. Maybe include a security setting where we can control who can use library sets through the script console. (Maybe even allow us to choose which library sets can be used through the console?) This could be very helpful in testing scripts.