docs: say that concurrent jobs on one runner each need their own builder_name - #386
Draft
dash14 wants to merge 1 commit into
Draft
docs: say that concurrent jobs on one runner each need their own builder_name#386dash14 wants to merge 1 commit into
builder_name#386dash14 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
builder_nameis what identifies the builder's containers, and setup tears down anything already running under that name before starting its own. Two jobs sharing a runner and the default name therefore destroy each other's builder, and the README never said so.Changes
builder_name, and why a GitHub-hosted runner does not need it.No behavioural change.