You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
looking at the phase2 buildworkers it looks like they rebuild all packages on a daily basis, using whatever SDK is available by that time. If I'm not mistaken, this introduces three pitfalls:
All packages are daily rebuild which requires a lot of time, even if only a few packages, may none, changed at all
A package in version 1.0 and release 4 may change from one day to the other based on different buildsystems. So even if it is the same release, it's maybe different package due to (possibly breaking) changes in the underlying build system.
Packages are builds with different buildsystem revisions, which makes it harder to reproduce them. For example when testing for reproducibility.
An alternative could be to rebuild only what's changed since the last build. The following two shell command give a list of all packages changed since the last build of packages.git. This can be used as an input for whatever build setup is used:
The package index creation currently happens on the worker, which would no longer be of much use as the worker no longer stores all packages locally. As the signing of packages via signall.sh happens on the control server anyway, it may as well run make package/index after the new packages where synced over.
This should dramatically reduce compile times for packages and would even allow a faster iteration than 24h, is desired.
The text was updated successfully, but these errors were encountered:
Hi all,
looking at the phase2 buildworkers it looks like they rebuild all packages on a daily basis, using whatever SDK is available by that time. If I'm not mistaken, this introduces three pitfalls:
An alternative could be to rebuild only what's changed since the last build. The following two shell command give a list of all packages changed since the last build of packages.git. This can be used as an input for whatever build setup is used:
The package index creation currently happens on the worker, which would no longer be of much use as the worker no longer stores all packages locally. As the signing of packages via
signall.sh
happens on the control server anyway, it may as well runmake package/index
after the new packages where synced over.This should dramatically reduce compile times for packages and would even allow a faster iteration than 24h, is desired.
The text was updated successfully, but these errors were encountered: