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

Revert "Resolve TA image reference at runtime" #102

Merged
merged 1 commit into from
Jul 10, 2024

Conversation

ralphbean
Copy link
Contributor

This reverts commit f229b13.

This was breaking ci in the build-definitions repo.

There, the latest release of this is pulled and used, which means that whenever a new trusted artifacts bundle is available, suddenly CI fails for all changes until those bundle references are updated and merged.

We should rely on renovate to bump those references, like other bundle references so we can manage it in a controlled fashion.

This reverts commit f229b13.

This was breaking ci in the build-definitions repo.

There, the `latest` release of this is pulled and used, which means that
whenever a new trusted artifacts bundle is available, suddenly CI fails
for *all* changes until those bundle references are updated and merged.

We should rely on renovate to bump those references, like other bundle
references so we can manage it in a controlled fashion.
@zregvart
Copy link
Member

We should rely on renovate to bump those references, like other bundle references so we can manage it in a controlled fashion.

Renovate didn't do a good job at it in konflux-ci/build-definitions#1137, I was thinking this wasn't the best idea, and decided to go for it as we do not update build-trusted-artifacts that often.

@zregvart zregvart merged commit cd86f5f into enterprise-contract:main Jul 10, 2024
1 check passed
@zregvart
Copy link
Member

The downside of reverting this is that the image will always revert to quay.io/redhat-appstudio/build-trusted-artifacts:latest@sha256:4e39fb97f4444c2946944482df47b39c5bbc195c54c6560b0647635f553ab23d

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.

2 participants