CI: Rework gvmd build container image #2138
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change the gvmd-build container image build to be independent of changes and releases of gvmd itself. The images only need to be rebuild if gvm-libs has changed or if the base container image has new packages for the dependencies. Therefore it isn't required to rebuild them on every release, pull request or push. Now only two flavors of the gvmd-build image exist. First gvmd-build:stable which is based on the latest gvm-libs release and second gvmd-build:edge which is based on the latest changes in gvm-libs.
Conventional Commits Report😢 No conventional commits found. 👉 Learn more about the conventional commits usage at Greenbone. |
timopollmeier
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Rework gvmd build container image
Why
Change the gvmd-build container image build to be independent of changes and releases of gvmd itself. The images only need to be rebuild if gvm-libs has changed or if the base container image has new packages for the dependencies. Therefore it isn't required to rebuild them on every release, pull request or push.
Now only two flavors of the gvmd-build image exist. First gvmd-build:stable which is based on the latest gvm-libs release and second gvmd-build:edge which is based on the latest changes in gvm-libs.
References
GEA-441