-
Notifications
You must be signed in to change notification settings - Fork 0
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
rocks: publish jobs should not overwrite images with the same tag unless forced #32
Labels
enhancement
New feature or request
Comments
This was referenced Dec 6, 2023
orfeas-k
changed the title
Make sure publish jobs do not overwrite images with the same tag unless forced
rocks: publish jobs should not overwrite images with the same tag unless forced
Dec 6, 2023
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5128.
|
orfeas-k
added a commit
that referenced
this issue
Dec 14, 2023
* Add `publish-rock.yaml` workflow * Add `integration-test-rock.yaml` workflow * Add `sanity-test-rock.yaml` workflow * Add `scan-rock.yaml` workflow * Add `build-rock.yaml` workflow * Rename `build-scan-test` to `build-scan-test-publish.yaml` * Make `publish-rock.yaml` check if Docker image exists * Rename to `get-rocks-modified.yaml` (replace `_` with `-`) * Rename to `get-rocks-modified-and-build-scan-test-publish.yaml` (replace `_` with `-`) * Rename `build-scan-and-test-rock.yaml` to `build-scan-test-publish-rock.yaml` * Refactor `build-scan-test-publish-rock.yaml` to call reusable WFs * Refactor `build_and_publish_rock.yaml` to call reusable WFs * Add `python-version` as input to `integration-test` WF Refs #31 Closes #28 Closes #32 Closes #35
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What needs to get done
Update CI to check and abort publishing if an image with the same tag exists.
Why it needs to get done
Since a publish job can be triggered on dispatch, it is possible it will try to publish an image with a tag while there is already one published.
We should update our publish workflows (one is here) in order to make sure our CI protects us from this, since this is a mistake that can happen in silence.
The text was updated successfully, but these errors were encountered: