This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
CI: Prime docker cache in "Docker cache build" job #18438
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @leezu , Thanks for submitting the PR
CI supported jobs: [clang, windows-cpu, centos-cpu, edge, unix-cpu, miscellaneous, sanity, website, centos-gpu, unix-gpu, windows-gpu] Note: |
Cache priming was previously only handled when using the ./ci/build.py or ./ci/docker_cache.py script. The former is used during most CI jobs. The latter is used for containers not declared in docker-compose.yml during the "Docker cache build" job. As more and more containers are declared in docker-compose.yml, we need to fix the cache priming issue.
szha
approved these changes
May 29, 2020
marcoabreu
approved these changes
May 29, 2020
|
@mxnet-bot run ci [unix-cpu] |
|
Jenkins CI successfully triggered : [unix-cpu] |
yijunc
pushed a commit
to yijunc/incubator-mxnet
that referenced
this pull request
Jun 9, 2020
Cache priming was previously only handled when using the ./ci/build.py or ./ci/docker_cache.py script. The former is used during most CI jobs. The latter is used for containers not declared in docker-compose.yml during the "Docker cache build" job. More and more containers are declared in docker-compose.yml now, but prior to this commit their cache wasn't primed in the "Docker cache build" job.
AntiZpvoh
pushed a commit
to AntiZpvoh/incubator-mxnet
that referenced
this pull request
Jul 6, 2020
Cache priming was previously only handled when using the ./ci/build.py or ./ci/docker_cache.py script. The former is used during most CI jobs. The latter is used for containers not declared in docker-compose.yml during the "Docker cache build" job. More and more containers are declared in docker-compose.yml now, but prior to this commit their cache wasn't primed in the "Docker cache build" job.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cache priming was previously only handled when using the ./ci/build.py or
./ci/docker_cache.py script. The former is used during most CI jobs. The latter
is used for containers not declared in docker-compose.yml during the "Docker
cache build" job. As more and more containers are declared in
docker-compose.yml, we need to fix the cache priming issue.