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

Aggregate multiple machines to one launch #183

Open
kflore16 opened this issue Dec 5, 2023 · 0 comments
Open

Aggregate multiple machines to one launch #183

kflore16 opened this issue Dec 5, 2023 · 0 comments
Assignees

Comments

@kflore16
Copy link

kflore16 commented Dec 5, 2023

Is this possible and would this be handled by client-javascript? I'm able to do so in a CI/CD pipeline by having a step that creates the launch then propagate the launch ID created to the workers/containers. My dilemma is here:

  1. If using another pipeline step to call finishLaunch, the duration would be incorrect as there would still be items being processed/reported. The individual workers/containers would not technically finish the launch themselves since they are already specifying an existing launch and items still get reported accordingly.
  2. Have the containers somehow "poll" the last item's reported status using the API and then call either finish launch OR do nothing if there exists items being processed.
  3. Some other methods unbeknownst to me
@AmsterGet AmsterGet self-assigned this Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants