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
adding persistent template test and updating some #1302
adding persistent template test and updating some #1302
Conversation
jitendar-singh
commented
Jul 8, 2021
- Adding test for persistent template
- Adding scenario to tear down the test project for all resources created while testing the ephemeral template
- Adding maven agent test for persistent template
- Adding nodejs agent test for persistent template
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.
Aside from the PV related suggestions below @jitendar-singh
- outside of this PR, but ideally sooner rather than later, if you are not already on this path, I'd love to see all this cool stuff you are doing invoked from CI for any PRs against this repo
- I could also see use defining periodic / batch jobs of the smoke tests against various versions of openshift
- a few pointers from what we do in other repos that could help get you started
https://github.com/openshift/release/blob/master/ci-operator/config/openshift/builder/openshift-builder-master.yaml#L52-L59
https://github.com/openshift/release/blob/master/ci-operator/config/openshift/csi-driver-projected-resource/openshift-csi-driver-projected-resource-master.yaml#L44-L65
and add analogous entries for the smoke tests to
https://github.com/openshift/release/blob/master/ci-operator/jobs/openshift/jenkins/openshift-jenkins-master-presubmits.yaml
and
https://github.com/openshift/release/blob/master/ci-operator/config/openshift/jenkins/openshift-jenkins-master.yaml
Otherwise, I'm certainly not fluent enough in python to offer you stylistic / detailed comments on that actual code. To some extent, being able to run them from CI with repetition and consistency would be the true validation for me.
@@ -0,0 +1,22 @@ | |||
Feature: Deploy Jenkins with persistent volume on openshift using template based install |
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.
So best as I can tell, this test assumes the persistent volumes are created prior to the invocation of the test.
If that is correct @jitendar-singh I believe that should be explicitly called out here and in the other persistent*.feature files.
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.
Or, ideally, you replicate the NFS based PV setup we do in the current extended tests at https://github.com/openshift/origin/blob/master/test/extended/builds/pipeline_jenkins_e2e.go#L60-L72
Then we could be on a path of removing those persistent template tests in openshift/origin and replace them with CI invocations of your new smoke tests.
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 @gabemontero I will work this next.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jitendar-singh, jkhelil 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 |