Skip to content
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

Strengthen build-arch rebuild capabilities #566

Open
jlebon opened this issue Jul 18, 2022 · 4 comments
Open

Strengthen build-arch rebuild capabilities #566

jlebon opened this issue Jul 18, 2022 · 4 comments
Labels
enhancement New feature or request low_priority

Comments

@jlebon
Copy link
Member

jlebon commented Jul 18, 2022

Right now, if build-arch fails, one can mostly rerun it with the same parameters. There is one gotcha: if the failure happens at any point after the Archive step, the artifacts for the given build ID and arch will already exist.

We should strengthen the job so that it handles this window better.

@jlebon
Copy link
Member Author

jlebon commented Jul 18, 2022

One simple solution @dustymabe and I we came up with is to check upfront if the artifacts already exist, and if so just skip straight to the Sign Images step.

@jlebon
Copy link
Member Author

jlebon commented May 16, 2023

A temporary hack on this is to have a salvage-build job that we can run manually that just fetches the artifacts of a build, signs them, emits the compose repo import, and schedules the follo-wup kola jobs.

@prestist prestist added the enhancement New feature or request label Jun 29, 2023
@prestist
Copy link
Contributor

This might be a bit complicated, for little gain; revisit with @jlebon; This #566 (comment) seems the most relevant.

@jschintag
Copy link
Contributor

One option is to have the steps that notifies the ostree repo to be a warning instead of a failure, saving us from having to run cloud and update tests manually for the build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low_priority
Projects
None yet
Development

No branches or pull requests

3 participants