[CI] Refactor Jenkins CI pipeline + migrate all Linux tests to Jenkins #4401
Conversation
|
@CodingCat Can you look at this? In particular, I'd like to seek your feedback to the cross-version checks, where XGBoost4J JARs are tested against JDK 8, 11, and 12. See https://xgboost-ci.net/blue/organizations/jenkins/hcho3-xgboost-ci-test/detail/refactor_jenkins/107/pipeline/203 for an example of JVM test. (Note: Spark tests are only run for JDK 8 for now) |
hcho3
changed the title
|
LGTM for jvm-packages part |
|
@CodingCat FYI, this PR is adding a dummy project named xgboost4j-tester under jvm-packages. This is needed so that I can run code from xgboost4j-example |
that's fine, we can use it for more integration test in future |
|
TODO: write a short doc explaining what |
hcho3
force-pushed
the
refactor_jenkins
branch
2 times, most recently
from
defeb50
to
8d81b24
Compare
|
@trivialfis I found the fix for leak detector: google/sanitizers#764. I need to add PTRACE capability to docker runs. |
|
Re-basing against the latest master to fix Windows tests |
|
Running two Spark jobs in a row resulted in #4406, so I'm disabling the second Spark integration test for now |
|
Will try to fix Mac CMake build issue in a follow-up PR |
|
Merged. Thanks everyone! |
dmlc#4401) * All Linux tests are now in Jenkins CI * Tests are now de-coupled from builds. We can now build XGBoost with one version of CUDA/JDK and test it with another version of CUDA/JDK * Builds (compilation) are significantly faster because 1) They use C5 instances with faster CPU cores; and 2) build environment setup is cached using Docker containers
See #4234 for details.
Note that builds (compilation) are significantly faster because