Uh oh!
There was an error while loading. Please reload this page.
[master] Jenkinsfile: use docker/docker instead of docker/engine - #461
Merged
Conversation
thaJeztah
commented
Apr 30, 2020
MemberAuthor
@tiborvass PTAL |
thaJeztah
commented
Apr 30, 2020
MemberAuthor
Ah, dang; looks like I didn't split the commits correctly |
The release branches have moved back to the upstream docker/docker repository, so we should use that as source instead of the docker/engine fork (and rely on it being synced with upstream) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
thaJeztahforce-pushed
the
use_docker_docker
branch
from
April 30, 2020 17:07
86c5c23 to
30635cbComparethaJeztah
commented
Apr 30, 2020
MemberAuthor
Should be fixed now |
tiborvass
approved these changes
May 1, 2020
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
extracted from #457
The release branches have moved back to the upstream docker/docker
repository, so we should use that as source instead of the docker/engine
fork (and rely on it being synced with upstream)