-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
submodule update --recursive failed #2598
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/kind bug |
fyi @ad22 this looks possibly related to the refactoring added to git-init? |
Appears so. I'll attempt to fix it. Edit: Looking at the line reported, that's a pretty embarrassing typo. There was probably no test to catch it either. |
ad22
pushed a commit
to ad22/pipeline
that referenced
this issue
May 11, 2020
tekton-robot
pushed a commit
that referenced
this issue
May 12, 2020
afrittoli
pushed a commit
to afrittoli/pipeline
that referenced
this issue
May 14, 2020
tekton-robot
pushed a commit
that referenced
this issue
May 14, 2020
This was fixed in #2602 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
it should append --depth only once
Actual Behavior
"Error running git [submodule update --recursive --depth --depth=1]: exit status 1\nfatal: depth --depth=1 is not a positive number
https://github.com/tektoncd/pipeline/blob/master/pkg/git/git.go#L172
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-21T01:25:41Z", GoVersion:"go1.13.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.9", GitCommit:"2e808b7cb054ee242b68e62455323aa783991f03", GitTreeState:"clean", BuildDate:"2020-01-18T23:24:23Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Tekton Pipeline version:
v0.12.0
The text was updated successfully, but these errors were encountered: