-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add helm charts & build publish workflows #6
Conversation
5273693
to
32f5656
Compare
cbf2631
to
0de81b5
Compare
.github/workflows/tests.yml
Outdated
@@ -1,182 +0,0 @@ | |||
name: CI |
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.
Renamed file to xp.yml and added build/publish steps to new file.
# - build-management-service | ||
# - build-treatment-service | ||
# - release-rules | ||
# uses: gojek/xp/.github/workflows/release.yml@main |
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.
To uncomment release action in subsequent PR.
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.
Apologies on the delayed review. On the whole it LGTM. I left some comments for changes.
.github/workflows/xp.yml
Outdated
path: ui/build/ | ||
retention-days: ${{ env.ARTIFACT_RETENTION_DAYS }} | ||
|
||
build-management-service: |
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.
Can we combine this with the publish step ? In turing, the build / publish separation makes sense because the built docker images are used in the e2e tests. We don't need to build the docker images ahead of time for XP, right? The built API binaries from the e2e-tests
job can be saved as artifacts for reuse. Then, during the publish phase, we can build the UI and subsequently use the API binaries in the docker image for the management service. Similar steps for the treatment service minus the UI.
42d7e0b
to
52ad965
Compare
52ad965
to
047efe4
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.
LGTM. 🚀
What this PR does / why we need it:
This PR adds helm charts for both Management and Treatment Services. In addition, build and publish steps are added to Github Actions workflow for generation of the services' artifacts.
Which issue(s) this PR fixes:
NONE