Skip to content

Use worker pool for parallel jobs#4

Open
Robert-Furth wants to merge 11 commits intomasterfrom
parallel-worker-pool
Open

Use worker pool for parallel jobs#4
Robert-Furth wants to merge 11 commits intomasterfrom
parallel-worker-pool

Conversation

@Robert-Furth
Copy link

The previous version started all parallel jobs at once, no matter how many jobs there were. This behavior could lead to a huge number of docker containers all being run at once, which slowed down the host machine considerably. This PR fixes that issue by using a worker pool to limit the number of jobs that can be run in parallel. Currently, the maximum number is hardcoded to 4.

Robert-Furth and others added 11 commits July 20, 2021 23:03
Each workflow run has a UUID generated for it when it is started. This UUID is
added to the container name of each job in a run. This means that multiple
instances of act can run on the same workflow without their containers' names
conflicting.
* Add "/artifacts" as a mount

* Only remove job container if the job succeeds or if `--rm` given

Previously, the container would be removed no matter what. Now, users can leave
off the `--rm` flag to leave containers running if they fail, which can aid in
debugging.
The intended behavior is for 'include' directives to modify existing entries
if their common keys match, and to only add new entries if they cannot modify
any existing entry. Previously, 'include' directives had no effect if they had
no keys in common with an existing entry, and always added new entries if they
did.
When a workflow tries to run actions/checkout, the runner needs to know if the
workflow wants to check out the current repository or a remote repository. It
does this by comparing the provided repository name and ref with those of the
current branch. This commit expands expressions in those fields before the
comparison, so workflows can call actions/checkout with parameters like
"ref: {{ SOME_VARIABLE }}".
@ryanajae
Copy link

Does this increase the runtime significantly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants