Open
Conversation
4ac8674 to
61ad59f
Compare
61ad59f to
3368440
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
3368440 to
0dd4b48
Compare
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
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 an opt-in Git command tracing mode for Git sources so BuildKit can show the effective Git commands it's running during source resolution and checkout. This feature is disabled by default and can be enabled with
BUILDKIT_DEBUG_GIT_COMMANDS=1build-arg (similar toBUILDKIT_CONTEXT_KEEP_GIT_DIR).Main motivation relates to crazy-max/diun#1544 (comment). While working through Git source behavior differences around remote contexts, shallow fetches, tags, and
.gitpreservation, it became clear that the existing logs show Git output but don't make the executed commands themselves obvious. That makes troubleshooting slower than it should be, especially for remote Git contexts where the user only sees side effects such as fetched refs, detached HEAD messages, or cache hits without seeing the exactgit fetch,git checkout,git remote, orgit update-refcalls that produced them:Not sure if we should have a git query param to enable this like we do for
keep-git-dir? Maybedebug?