-
Notifications
You must be signed in to change notification settings - Fork 232
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
Integration tests on spark 3.0.1-SNAPSHOT & 3.1.0-SNAPSHOT #335
Conversation
Add Jenkinsfile for integration tests on spark 3.0.1-SNAPSHOT & 3.10.-SNAPSHOT
build |
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.
There's a lot of duplication across Jenkins files. Not must-fix for this PR, but it would be nice to have a followup to refactor this if possible. Otherwise every time we want to tweak something in the integration test pipelines we need to remember to make that same change in a bunch of other files (e.g.: updating the slack
method).
Good suggestion! |
47d7e4e
to
4aa647d
Compare
build |
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.
Since @jlowe is out for a bit longer and it looks like his requests were all addressed I think we can merge this in.
build |
* Integration tests on spark 3.0.1-SNAPSHOT & 3.10.-SNAPSHOT Add Jenkinsfile for integration tests on spark 3.0.1-SNAPSHOT & 3.10.-SNAPSHOT * Fix copyright and spark version anotations Co-authored-by: Tim Liu <timl@nvidia.com>
* Integration tests on spark 3.0.1-SNAPSHOT & 3.10.-SNAPSHOT Add Jenkinsfile for integration tests on spark 3.0.1-SNAPSHOT & 3.10.-SNAPSHOT * Fix copyright and spark version anotations Co-authored-by: Tim Liu <timl@nvidia.com>
Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
1, Add integration tests Jenkinsfile on spark 3.0.1-SNAPSHOT & 3.1.0-SNAPSHOT
2, Only update Jenkins scripts, no source change. No unit tests needed.
3, No Github issue related to the PR.