-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix regression: can fetch branches and tags references without specifying commit hashes for private git repository used as context #1823
Conversation
Rescan needed from a repository manager (post CLA signature). Thanks ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but would it be possible to add an integration test to ensure this behavior doesn't regress in a future change?
Thanks @imjasonh for the review. Regarding implementing some integration tests, this would mean adding a test involving the build from a private repository, so that the authentication is required. Right now, Kaniko GitHub repository is used in the integration tests to check the git context from a public repository. I could definitely add some integration tests involving a local git server, the same way the use of a local registry is described in the Development guide (in this case, using a docker image of Gogs for example could be an option, as it is very easy to setup). What do you think ? |
Makes sense. If this causes more trouble in the future we can add a test then. Can you rebase on Thanks for this contribution, and for your patience! |
Thanks! |
9ba9f97
to
572584f
Compare
Thank you @imjasonh and @gcalmettes for working on this! The bug was quite annoying for us. |
Fixes #1801
Description
This PR fixes a regression introduced in #1765 (PR released in
v1.7.0
) that led to the need of always specifying a commit hash even for tags or branches references, when agit
source context was used.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Reviewer Notes