-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Git artifacts detached from revision #10018
Comments
We changed the Git library in v3.4. That is probably the cause, but a revert isn’t going to happen anytime soon. I think there might be a workaround. Have you tried |
Also, please make sure you don’t have both a label and branch with the same name. Git does allow that. |
Hi @alexec , thanks for the update. I'll give
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Pre-requisites
:latest
What happened/what you expected to happen?
When using a standard git input artifact in Argo Workflows v3.4.3 or latest to clone a repository, the resulting source directory will not be on the branch that was cloned.
If you were to exec into the container that ran a git clone and run
git branch
you will see (based on the workflow I provided),We recently upgraded from v3.2.7 where the clone would have been on the branch
feature/2022q4
based on the sample workflow I've provided.Version
v3.4.3
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
I ran,
but as far as I can tell nothing related to this git clone was logged.
Logs from in your workflow's wait container
I ran the following because this workflow completes successfully. There are no errors in any of these steps.
The text was updated successfully, but these errors were encountered: