This repository was archived by the owner on Jul 18, 2025. It is now read-only.
Extra options for "build" sections in YAML #512
Merged
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
type/marshal logic Signed-off-by: Nathan Sullivan <[email protected]>
Signed-off-by: Nathan Sullivan <[email protected]>
Signed-off-by: Nathan Sullivan <[email protected]>
Signed-off-by: Nathan Sullivan <[email protected]>
Contributor
Author
|
Now that's interesting, the acceptance tests fail yet Jenkins passes? |
Contributor
|
@CpuID yes, the acceptance tests is merely there to see how close (or not) we are to support the full range of |
Contributor
Author
|
np thx, calling "mission accomplished" in that case :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Adds support under the
buildheading for:cache_fromlabelsnetworktargetNote:
networkis undocumented in the docker-compose.yml reference but is supported and works (as of config version 3.4).@vdemeester do we also need these in docker/service/service.go?