-
Notifications
You must be signed in to change notification settings - Fork 59
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
Use build submodule and adapt CI pipeline #72
Conversation
Signed-off-by: Hasan Turken <turkenh@gmail.com>
Signed-off-by: Hasan Turken <turkenh@gmail.com>
Signed-off-by: Hasan Turken <turkenh@gmail.com>
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.
Overall looks great, left a couple of comments
Signed-off-by: Hasan Turken <turkenh@gmail.com>
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.
Looks great 👍
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 @turkenh, thanks for adding this! from your PR notes, it looks like the CI integration will be tested after merge. Anything else you think we can do to verify before merging? If not, I think you have permissions to merge yourself now :)
We will need to add the following repo secrets before merge: XPKG_ACCESS_ID and XPKG_TOKEN |
Description of your changes
This PR uses upbound/build submodule to build and publish configuration package (specifically upbound/build#203 and upbound/build#207).
It also adapts CI pipeline accordingly.
I have:
How has this code been tested
Ensure package is build under
_output/xpkg
CI needs to be tested after merge.