Skip to content

Conversation

@jacobweinstock
Copy link
Member

Description

Because of the way CI is built (2 self-hosted runners), CI was not pushing container images when building on main. This was because PR's would build the images and the would be locally in the Docker cache. Then when main ran, hook-lk containers.sh would run and see that the image existed in the local Docker cache already and stop before pushing.

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

Because of the way CI is built (2 self-hosted runners),
CI was not pushing container images when building on main.
This was because PR's would build the images and the would
be locally in the Docker cache. Then when main ran,
hook-lk-containers.sh would run and see that the image
existed in the local Docker cache already and stop before
pushing.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
@jacobweinstock jacobweinstock merged commit 74e114f into tinkerbell:main May 17, 2024
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 this pull request may close these issues.

1 participant