Skip to content
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

Stagger schedule triggers so that there is less contention on pushes #332

Open
ianlewis opened this issue Feb 27, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@ianlewis
Copy link
Member

ianlewis commented Feb 27, 2024

Bootstrap scripts often have race conditions where two runs push changes to the repo at the same time causing the push to fail. e2e-bootstrap.sh implements retries to help alleviate the issue but it would be good to stagger the schedule triggers by a few minutes to further help with the problem.

The error shows up in logs like the following:

To https://github.com/slsa-framework/example-package.git
 ! [rejected]          main -> main (fetch first)
error: failed to push some refs to 'https://github.com/slsa-framework/example-package.git'
hint: Updates were rejected because the remote contains work that you do not
hint: have locally. This is usually caused by another repository pushing to
hint: the same ref. If you want to integrate the remote changes, use
hint: 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
@ianlewis ianlewis added the enhancement New feature or request label Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant