-
Notifications
You must be signed in to change notification settings - Fork 9
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
Change build order slightly #212
Change build order slightly #212
Comments
Hey @jonathanspw, first, thanks for this suggestion. We have talked about this and these are our thoughts. This involves factoring the SRPM build out of the current build process and make it a separate first step, this is:
It would involve some non-trivial refactoring of our current workflow, but we believe that this won't only be beneficial in building (or failing) speed, but also, it's a good opportunity for us to simplify the current logic around the It would also involve updating the UI to reflect the changes. Right now, we have this: And when looking at build logs, we get this: After the changes are made in backend, we'd need to:
|
When doing parallel builds currently we have to wait on the first build (x86 generally) to finish before the other builds can start, so that they all use the same SRPM. This creates unnecessary delays which is particularly frustrating when doing builds by hand for testing, etc.
SRPM generation is very fast relative to full builds, so it would make the most sense to have a dedicated step for building the SRPM, then trigger all of the builds at once. The result should basically be that builds take half as long because you're not waiting on the first build to finish before running the rest, only the SRPM build.
Mentioned this briefly to @javihernandez in Brussels and I think he understands what I'm getting at here.
The text was updated successfully, but these errors were encountered: