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

Run Checkums post-submit as follow-up to Builder Base post-submit #781

Open
danbudris opened this issue Jan 20, 2023 · 2 comments
Open

Run Checkums post-submit as follow-up to Builder Base post-submit #781

danbudris opened this issue Jan 20, 2023 · 2 comments
Assignees

Comments

@danbudris
Copy link
Member

danbudris commented Jan 20, 2023

When the builder-base post-submit runs, we should follow up with an execution of the checksums execution (the attribution job) in a post-submit.

Right now we run the checkums in a nightly periodic, or we manually trigger them when material changes are made to the builder-base, such as updating the versions of dependencies. This step is required prior to updating the EKS-A and EKS-D prow jobs to use the builder-base as their base image, otherwise the checksums will be mismatched and the prow jobs will fail.

However, we want to ensure that when a new builder-base is published, new checksums are published automatically in response. We can do this by triggering the checksums job FROM the builder-base post-submit, updating the checkusm job to use the just-published builder-base image tag.

This will ensure that when a new builder-base image is published, the correct checksums are published ASAP, and we can move forward with the prow job updates sooner rather than later and elminate a manual step which we've been prone to miss.

AC:

  • the checksums job runs automatically in response to a new builder-base image being published
  • the description of the prow job PRs should include links to the newly trigger checksum jobs
@danbudris
Copy link
Member Author

danbudris commented Jan 20, 2023

some thoughts: this could be done by executing a kubectl apply of the checksums prow-job yaml at the end of the builder-base post-submit. We'd just need to use a template that we could over-ride the image on so taht the applied job was running using the just-published builder-base image as the job image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants