Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run on N targets in role #4159

Closed
droyad opened this issue Jan 15, 2018 · 9 comments

Comments

@droyad
Copy link
Contributor

commented Jan 15, 2018

At the moment a step runs on all targets in a role. If a user wants to run a step only once, they either:

  • Choose one of the targets and assign a special role, which causes problems if that target is unhealthy
  • Run the script on the server, which may not be optimal, e.g. as it could be in the wrong network segment

We should allow the user to specify the maximum number of targets to run the step on.

UI Changes

The Execution Plan section currently looks like this:

image

We should re-work this into something like:

image

Once Workers #4158 is a thing Octopus Server would be replaced by In Pool ...

@martynakaminska

This comment has been minimized.

Copy link

commented Aug 14, 2018

👍
Are we aware when this will be implemented?

@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Aug 20, 2018

@martynakaminska What is the scenario where you would find this feature useful? We have implemented workers (#4158), and that covers a lot of what is discussed above.

@martynakaminska

This comment has been minimized.

Copy link

commented Sep 3, 2018

What we see as problem that we are using Deploy Package step to deploy AWS Lambda functions. Unfortunately you can't run this step against workers

@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2018

@martynakaminska Does this all happen in one step, or do you need to chain multiple steps together?

If it is one step, the "Run Script From Package" step might do what you need, particularly with the latest changes

@martynakaminska

This comment has been minimized.

Copy link

commented Sep 5, 2018

Thanks. It would help but this step doesn't have Feature to perform transform of variables in files. However we found out that "Run an AWS CLI Script" step has this functionality, can run from package and can be run on Worker. This solves our issue.

@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 6, 2018

Awesome you got it going. The Substitution options for normal script steps were added in 2018.8.0 if I remember correctly.

@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 6, 2018

Closing this as we do not plan on implementing this in light of #4842

@lock

This comment has been minimized.

Copy link

commented Dec 5, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.