-
Notifications
You must be signed in to change notification settings - Fork 73
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
enable pairing with branches from ksctl repository #1030
enable pairing with branches from ksctl repository #1030
Conversation
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.
👍
/retest |
Quality Gate passedIssues Measures |
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 👍
Thanks a lot for creating this and for answering my comments!
minor note - maybe we could document somewhere these variables:
USE_INSTALLED_KSCTL=true
would use the installed ksctl version
KSCTL_REPO_PATH=/my/local/path/to/ksctl/
would build your local version of ksctl
WDYT?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexeykazakov, MatousJobanek, mfrancisc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
74da2b9
into
codeready-toolchain:master
With [PR redhat-appstudio#1030] landing in toolchain-e2e, tests now will try to pair an open PR against toolchain-e2e with an open PR against [ksctl]. We're always going to run tests with the latest version of ksctl, so we should install it before deploying member-operator. [PR redhat-appstudio#1030]: codeready-toolchain/toolchain-e2e#1030 [ksctl]: https://github.com/kubesaw/ksctl/ Signed-off-by: Andy Sadler <[email protected]>
With [PR redhat-appstudio#1030] landing in toolchain-e2e, tests now will try to pair an open PR against toolchain-e2e with an open PR against [ksctl]. We're always going to run tests with the latest version of ksctl, so we should install it before deploying member-operator. [PR redhat-appstudio#1030]: codeready-toolchain/toolchain-e2e#1030 [ksctl]: https://github.com/kubesaw/ksctl/ Signed-off-by: Andy Sadler <[email protected]>
With [PR redhat-appstudio#1030] landing in toolchain-e2e, tests now will try to pair an open PR against toolchain-e2e with an open PR against [ksctl]. We're always going to run tests with the latest version of ksctl, so we should install it before deploying member-operator. [PR redhat-appstudio#1030]: codeready-toolchain/toolchain-e2e#1030 [ksctl]: https://github.com/kubesaw/ksctl/ Signed-off-by: Andy Sadler <[email protected]>
With [PR redhat-appstudio#1030] landing in toolchain-e2e, tests now will try to pair an open PR against toolchain-e2e with an open PR against [ksctl]. We're always going to run tests with the latest version of ksctl, so we should install it before deploying member-operator. [PR redhat-appstudio#1030]: codeready-toolchain/toolchain-e2e#1030 [ksctl]: https://github.com/kubesaw/ksctl/ Signed-off-by: Andy Sadler <[email protected]>
With [PR redhat-appstudio#1030] landing in toolchain-e2e, tests now will try to pair an open PR against toolchain-e2e with an open PR against [ksctl]. We're always going to run tests with the latest version of ksctl, so we should install it before deploying member-operator. [PR redhat-appstudio#1030]: codeready-toolchain/toolchain-e2e#1030 [ksctl]: https://github.com/kubesaw/ksctl/ Signed-off-by: Andy Sadler <[email protected]>
* install ksctl during kubesaw deployment With [PR #1030] landing in toolchain-e2e, tests now will try to pair an open PR against toolchain-e2e with an open PR against [ksctl]. We're always going to run tests with the latest version of ksctl, so we should install it before deploying member-operator. [PR #1030]: codeready-toolchain/toolchain-e2e#1030 [ksctl]: https://github.com/kubesaw/ksctl/ Signed-off-by: Andy Sadler <[email protected]> * install ksctl directly Signed-off-by: Andy Sadler <[email protected]> --------- Signed-off-by: Andy Sadler <[email protected]>
Since the e2e test setup is increasingly dependent on ksctl commands, I introduced a possibility of pairing between toolchain-e2e and ksctl.
USE_INSTALLED_KSCTL
orKSCTL_REPO_PATH
. The UX can be changed later.paired PR kubesaw/ksctl#58 (expecting to fail when generating tier manifests)