-
Notifications
You must be signed in to change notification settings - Fork 117
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
Create container images from the latest non-dev copr build #1751
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As agreed on the chat, let's pick the latest tmt
from Fedora stable repos instead. This will also remove the need for the manual copr
build.
a2c6c99
to
9ae6a44
Compare
9ae6a44
to
a85b0f5
Compare
a85b0f5
to
b655279
Compare
Any plans with this one, @lukaszachy? |
@psss If we go by previous agreement it means one needs to remember building a new image about a week after the release. I'll check if we didn't solve the problem by moving to hatch. Or if there isn't simpler fix. Waiting means we will forget. |
Yeah, using
What about installing the latest non-dev release from the copr repo? Could the exact rpm naming be used somehow? |
This seems to be working as expected:
It picks the latest stable version from the copr repo even if there is a newer
@lukaszachy, let's try it this way? |
b655279
to
bedecb3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be working fine.
@psss LGTM (I can't provide approval for (according to the github) my PR) |
Good, thanks for having a look! |
bedecb3
to
99d5807
Compare
/packit test -i full |
Once the stable copr build is created we can move the `quay` branch to trigger the new container images creation. Also fix an outdated link and remove irrelevant mention about the `post-upstream-clone` action which is no more used in `.packit.yaml` config.
99d5807
to
009fc0b
Compare
/packit test -i full |
Packit is producing y+1.dev versions however we want to have one with matching release in the container.
No idea yet how to avoid the manual 'copr build' step :/