Open wrussell1999 opened 2 months ago
This appears to also impact io.kestra.plugin.git.Push
as well. Running a flow multiple times at the same time (modifying different files simultaneously) will only generate a single commit.
A simple retry loop with a git pull; git push
solves this in other CICD style jobs on other platforms.
Expected Behavior
When using
EachParallel
to bulk commit multiple namespaces at once, all commits should appear in GitHub. If this is not possible due to the nature of committing multiple times to the same repository, it should fail or mentioned that it's not possible.Looks like Git PushFlows is rewriting the history, rather than pushing a new commit on top. If that's the intention, we should clear that up in the documentation as that prevents parallel use of PushFlows. This commit was accessed from the Kestra logs:![Screenshot 2024-06-20 at 17 18 26](https://github.com/kestra-io/plugin-git/assets/34094921/6bca012d-29fb-4b6e-acf2-be0c1c1051f8)
Actual Behaviour
When using![Screenshot 2024-06-20 at 17 17 21](https://github.com/kestra-io/plugin-git/assets/34094921/564d4c21-279b-4de8-a661-8b30034e8600)
EachParallel
to bulk commit multiple namespaces at once, it comes back as successful but not all of the commits are visible.Only one of the commits was successful:![Screenshot 2024-06-20 at 17 17 28](https://github.com/kestra-io/plugin-git/assets/34094921/c7ea4f76-c040-4f9c-8e59-66f1058606f1)
Steps To Reproduce
Environment Information
Example flow
No response