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
It takes about 1h right now for a full build. In the past few days, we've had to run and iterate the pipeline multiple times, and waiting for that 1h has been really painful at times. I think there are multiple ways we can speed this up:
first and foremost, while not related to a single build, we need to unblock concurrent builds (Allow concurrent builds #68)
parallelize buildextend commands -- this will likely require driving some changes into cosa. But at least for the ones that just do gf-platformid it shouldn't be too hard. Of course, this goes right into YAML/JSON interface for COSA coreos-assembler#531; cosa itself could potentially include the parallelization code.
The text was updated successfully, but these errors were encountered:
It takes about 1h right now for a full build. In the past few days, we've had to run and iterate the pipeline multiple times, and waiting for that 1h has been really painful at times. I think there are multiple ways we can speed this up:
xz
supports-T
for multi-threading. But doing this correctly for a k8s environment is tricky. See e.g. virt-install: do not assign vpu's when executed in Kubernetes coreos-assembler#284 (comment) and virt-install: do not assign vpu's when executed in Kubernetes coreos-assembler#284 (comment).gf-platformid
it shouldn't be too hard. Of course, this goes right into YAML/JSON interface for COSA coreos-assembler#531; cosa itself could potentially include the parallelization code.The text was updated successfully, but these errors were encountered: