This repository was archived by the owner on Oct 13, 2023. It is now read-only.
[17.06] Fix handling of remote "git@" notation#100
Merged
andrewhsu merged 2 commits intodocker-archive:17.06from Jul 12, 2017
andrewhsu:fix-build-git
Merged
[17.06] Fix handling of remote "git@" notation#100andrewhsu merged 2 commits intodocker-archive:17.06from andrewhsu:fix-build-git
andrewhsu merged 2 commits intodocker-archive:17.06from
andrewhsu:fix-build-git
Conversation
Member
|
CI is failing because of; Because it's not yet using Probably just adding these to imports should be sufficient; |
Contributor
Author
|
Added another commit to this PR with those imports. Looks like the unit tests now pass: |
`docker build` accepts remote repositories using either the `git://` notation, or `git@`. Docker attempted to parse both as an URL, however, `git@` is not an URL, but an argument to `git clone`. Go 1.7 silently ignored this, and managed to extract the needed information from these remotes, however, Go 1.8 does a more strict validation, and invalidated these. This patch adds a different path for `git@` remotes, to prevent them from being handled as URL (and invalidated). A test is also added, because there were no tests for handling of `git@` remotes. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 913eb99) Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
So that we don't have bring in the entire commit d3d1aab Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
docker-jenkins
pushed a commit
that referenced
this pull request
Mar 31, 2018
Add Bionic to README Upstream-commit: 9e33949 Component: packaging
docker-jenkins
pushed a commit
that referenced
this pull request
Oct 31, 2018
[18.09 backport] Fix incorrect spelling in error message Upstream-commit: 66bfae52bca82e6e3055ea5ce0203758af5364e9 Component: engine
silvin-lubecki
pushed a commit
to silvin-lubecki/docker-ce
that referenced
this pull request
Jan 30, 2020
Add Bionic to README
silvin-lubecki
pushed a commit
to silvin-lubecki/docker-ce
that referenced
this pull request
Feb 3, 2020
[17.06] Fix handling of remote "git@" notation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport fix from:
By cherry-pick of just the first commit, moby/moby@913eb99: