Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Parent issue for migrating Travis CI tasks to Docker and decoupling from Travis-specific environment variables and image state
Attachments
Issue Links
- is a parent of
-
ARROW-5466 [Java] Dockerize Java builds in Travis CI, run multiple JDKs in single entry
-
- Resolved
-
-
ARROW-5800 [R] Dockerize R Travis CI tests so they can be run anywhere via docker-compose
-
- Resolved
-
-
ARROW-5802 [CI] Dockerize "lint" Travis CI job
-
- Resolved
-
-
ARROW-5803 [C++] Dockerize C++ with clang 7 Travis CI unit test logic
-
- Resolved
-
-
ARROW-5809 [Rust] Dockerize (add to docker-compose) Rust Travis CI build
-
- Resolved
-
-
ARROW-5804 [C++] Dockerize C++ CI job with conda-forge toolchain, code coverage from Travis CI
-
- Closed
-
-
ARROW-5805 [Python] Dockerize (add to docker-compose) Python Travis CI job
-
- Closed
-
-
ARROW-5806 [CI] Dockerize (add to docker-compose) Integration tests Travis CI entry
-
- Closed
-
-
ARROW-5807 [JS] Dockerize NodeJS Travis CI entry
-
- Closed
-
-
ARROW-5808 [GLib][Ruby] Dockerize (add to docker-compose) current GLib + Ruby Travis CI entry
-
- Closed
-
-
ARROW-5810 [Go] Dockerize Travis CI Go build
-
- Closed
-
- is superceded by
-
ARROW-7101 [CI] Refactor docker-compose setup and use it with GitHub Actions
-
- Resolved
-