I suggest you...

Create jobs for recurring tasks. Use permissions to control task jobs by environment.

Create task jobs for recurring tasks. Use permissions to control task jobs by environment, project, node.

The QA Team could be assigned permissions on a task job to run an iisreset on all servers in the QA environment or particular projects in the environment. Dev Leads could restart Windows services on individual nodes in Dev. Right now a user has to be an Octopus admin to run a custom shell script but we don't want the Dev teams to be able to affect production. I'd rather just create a task job so Dev or QA does not mistakenly run the task on the wrong environment.

I know this is a deployment tool, not necessarily an automation tool. However a basic feature such as this would streamline deployments by allowing the dev and testing teams to self-service and minimizes risk for systems/application teams that support the tool.

26 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Brian C shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base