Skip to content
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

Migrate nightly&integration pipelines to blossom [skip ci] #862

Merged
merged 3 commits into from
Sep 29, 2020

Conversation

pxLi
Copy link
Collaborator

@pxLi pxLi commented Sep 27, 2020

Signed-off-by: Peixin Li pxli@nyu.edu

As per security requirement, we are going to move Jenkinsfiles to internal repo. This could bring us some headache if we want to make change to jenkinsfile, test scripts or dockerfile at the same time. (We have to make changes in different places) Feedback welcome :)

The real Jenkinsfiles comes here MR #1

The pipelines on blossom: rapids_nightly-0.3-github and rapids_integration-0.3-github

@pxLi pxLi added the build Related to CI / CD or cleanly building label Sep 27, 2020
@pxLi
Copy link
Collaborator Author

pxLi commented Sep 27, 2020

build

@pxLi
Copy link
Collaborator Author

pxLi commented Sep 27, 2020

since this PR brings some major changes to our CICD setup, @jlowe @revans2 @tgravescs plz help give some feedback thx! :)

@pxLi
Copy link
Collaborator Author

pxLi commented Sep 28, 2020

build

Copy link
Member

@jlowe jlowe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we expect a followup to remove all the jenkins/Jenkinsfile* files?

jenkins/Dockerfile.integration.centos7 Outdated Show resolved Hide resolved
jenkins/Dockerfile.integration.ubuntu16 Outdated Show resolved Hide resolved
jenkins/Dockerfile.ubuntu16 Outdated Show resolved Hide resolved
@pxLi
Copy link
Collaborator Author

pxLi commented Sep 28, 2020

Should we expect a followup to remove all the jenkins/Jenkinsfile* files?

@jlowe we will do it one by one since our reserved resource for all pipelines on blossom is not ready yet.
But yes, you can expect we will remove them all in coming days

@pxLi
Copy link
Collaborator Author

pxLi commented Sep 28, 2020

build

@pxLi
Copy link
Collaborator Author

pxLi commented Sep 29, 2020

build

@jlowe jlowe merged commit f6db85b into NVIDIA:branch-0.3 Sep 29, 2020
sperlingxx pushed a commit to sperlingxx/spark-rapids that referenced this pull request Nov 20, 2020
* migrate nightly to blossom

Signed-off-by: Peixin Li <pxli@nyu.edu>

* fix license 2019 and 2020 for dockerfiles

* fix ARGs in dockerfiles of integration test
nartal1 pushed a commit to nartal1/spark-rapids that referenced this pull request Jun 9, 2021
* migrate nightly to blossom

Signed-off-by: Peixin Li <pxli@nyu.edu>

* fix license 2019 and 2020 for dockerfiles

* fix ARGs in dockerfiles of integration test
nartal1 pushed a commit to nartal1/spark-rapids that referenced this pull request Jun 9, 2021
* migrate nightly to blossom

Signed-off-by: Peixin Li <pxli@nyu.edu>

* fix license 2019 and 2020 for dockerfiles

* fix ARGs in dockerfiles of integration test
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this pull request Nov 30, 2023
…IDIA#862)

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Related to CI / CD or cleanly building
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants