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.

Sign up for GitHub

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

Jump to bottom

scorecard-test-kuttl container image does not get pushed to container registry after release #6456

Open
andreasgerstmayr opened this issue Jun 2, 2023 · 9 comments
Open

scorecard-test-kuttl container image does not get pushed to container registry after release #6456

andreasgerstmayr opened this issue Jun 2, 2023 · 9 comments
Assignees
@everettraven
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
Backlog

Comments

@andreasgerstmayr
Copy link
Contributor

Bug Report

What did you do?

Submitted PR #6401 for the scorecard-test-kuttl container image, which got merged and is part of the recent operator-sdk v1.29.0 release.

What did you expect to see?

After the operator-sdk v1.29.0 release, the image should be pushed to quay.io at https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest

What did you see instead? Under which circumstances?

The container image was not pushed to quay.io: https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest

Possible Solution

Additional context

The master tag gets updated, and there are versions tagged which are higher than the operator-sdk version. I think it'd make sense to sync the scorecard-test-kuttl versions with the operator-sdk versions to avoid confusion.
@andreasgerstmayr andreasgerstmayr mentioned this issue Jun 2, 2023
Merged
2 tasks
@jberkhahn jberkhahn added this to the Backlog milestone Jun 5, 2023
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2023
@andreasgerstmayr
Copy link
Contributor Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2023
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 4, 2023
@andreasgerstmayr
Copy link
Contributor Author

/remove-lifecycle stale

the latest pushed tag is one year old :\

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 4, 2023
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2024
@andreasgerstmayr
Copy link
Contributor Author

still relevant

@andreasgerstmayr
Copy link
Contributor Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2024
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 3, 2024
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@everettraven everettraven

Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@andreasgerstmayr @openshift-bot @jberkhahn @everettraven