CI: build: throw away the previous build artifacts #159
Conversation
Keeping only the sstate an downloads between runs makes the result a bit more reproducible at the cost of having to do a bit more work per-run. Signed-off-by: Leonard Göhrs <l.goehrs@pengutronix.de>
|
Looks like 6:33 for https://github.com/linux-automation/meta-lxatac/actions/runs/10176907868/job/28147195616 (keep tmp/) and 8:23 for https://github.com/linux-automation/meta-lxatac/actions/runs/10177131999/job/28147911620 (remove tmp/) |
|
Not quite, but close. The 6:33 job actually built some things, while the 8:23 did not. I re-ran the first job to have a fair comparison: https://github.com/linux-automation/meta-lxatac/actions/runs/10176907868 Now it's 1:46 vs. 8:23. Both are acceptable CI build times in my opinion. I would nevertheless prefer to keep the build job as-is right now to gather some experience and to find out if it causes issues in practice. I am more than willing enough to troubleshoot those if they were to arise. |
|
I will close this PR until our builds fail catastrophically and I get tired of fixing them. |
Note
I am not convinced that this is a necessary or useful change.
I would personally prefer keeping the CI job as is.
This PR was mainly created to check what kind of impact such a change would have on the build time.
Keeping only the sstate an downloads between runs makes the result a bit more reproducible at the cost of having to do a bit more work per-run.