-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Package revision race #395
Comments
That's what I thought about when implemented existing revision number logic. I wanted to rely on external service like Redis with locking and releasing to avoid any possible race conditions around revision number like this. But with time, I must admit that it was over-engineering, rather then real case. |
Happened for the first time now with @Kami during the year or something 👍 |
I still think by implementing some locking and relying on external service would be overengineering. Solution for now: don't merge 2 PRs in one go. If that issue will happen again and again, - then yes worth adding some external Consul or Redis or whatever for revision locking. |
Update: the race happened one more time during the 2.4 release when we trigger the build for both |
Between fetching a revision number as a part of checkout and uploading a new package with this revision during deploy, every parallel package build will end up with the same revision number and will fail on deploy stage due to package already being present.
The text was updated successfully, but these errors were encountered: