Add a CI workflow for ETOS suite starter #25
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
This workflow will run when a PR is merged, it will build the docker image with the current SHA as tag and push it to the registry. After the image has been pushed it will update the image version in the manifests and push them to main.
fredjn
approved these changes
Nov 24, 2023
This was referenced Nov 24, 2023
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.
Applicable Issues
eiffel-community/etos#197
Description of the Change
This workflow will run when a PR is merged, it will build the docker image with the current SHA as tag and push it to the registry.
After the image has been pushed it will update the image version in the manifests and push them to main.
Alternate Designs
None that I can think of
Benefits
This will allow us to have fresh builds of the suite builder every time we merge to main, this will also allow us to track the main branch in our gitops tools.
Possible Drawbacks
We will build a lot more containers. But before we created a release often where we built a container.
This style probably won't work with the ESR and LogListener containers though, so we need to look into how to build and release them. I think we can solve it by defining the configmap (that we create in the kustomization file in this repository) in the suite runner repository and link it into the suite starter instead.
Sign-off
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Signed-off-by: Tobias Persson [email protected]