-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Run UATs from a remote commit #67
Conversation
Add option to run tests either from: * a remote branch of charmed-kubeflow-uats repository. * the local copy of the repository
@orfeas-k would it be possible to run a git command and detect the commit from which the test runs, and then use this to fetch from when running remotely? Essentially to avoid having folks to define the branch/commit manually and have the driver code detect the commit and tell it to the remote code. But this is a high level comment, and maybe not feasible depending on how the code is executed in the remote. |
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.
thanks @orfeas-k , some small comments
e5e2a7b
to
71fc6d4
Compare
Remove `branch` option and automatically grab currently checked out commit and use that for remote. Details in #65
71fc6d4
to
68482cd
Compare
@kimwnasptd Changed implementation to grab the checked out commit from the local repository and use this to sync the tests in the created volume. If the commit doesnt exist, tests will fail and log |
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!
Update UATs environment used in `full-bundle-tests.yaml` used after changes in canonical/charmed-kubeflow-uats#67.
This PR fixes #65. Implemented solution is described in #65 (comment). It essentially add the option of running tests either from:
charmed-kubeflow-uats
repository.Closes #65
Testing
In order to test this, one needs to:
tox -e kubeflow-local
.tox -e kubeflow-remote -- --branch kf-5473-add-remote-option
.That being said, I 've tested option 2 in an AKS cluster only (it works) and it will be tested also by the CI once it is implemented in canonical/bundle-kubeflow#850. It should work in EKS too but if it doesn't, we already have a different issue for EKS #55 and a task too canonical/bundle-kubeflow#802, thus if it doesn't work, it will be tackled as part of those efforts.