This is an automated email from the ASF dual-hosted git repository.
tqchen pushed a change to branch jenkins-s3-bundle-refactor
in repository https://gitbox.apache.org/repos/asf/tvm.git
discard 685ebefe16 [CI][REFACTOR] Centralize image lookup in
determine_docker_images.py
discard ce694e145a [CI][REFACTOR] data.py drops docker image registry entirely
discard e5ab67f8c7 [CI][FIX] Use existing ci/jenkins/docker-images.ini, drop
duplicate
discard 6df22c09b9 [CI][REFACTOR] Move docker image tags from
ci/jenkins/data.py to ci/docker-images.ini
discard 10950ac192 [CI][REFACTOR] Data-driven artifact stashing: s3.py
--bundle flag
add 29ffe6726d [CI][REFACTOR] Decouple Jenkins script from artifact paths
and image tags
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (685ebefe16)
\
N -- N -- N refs/heads/jenkins-s3-bundle-refactor (29ffe6726d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
ci/jenkins/data.py | 7 ++++---
ci/jenkins/generated/cpu_jenkinsfile.groovy | 4 ++--
ci/jenkins/generated/gpu_jenkinsfile.groovy | 4 ++--
ci/jenkins/templates/cpu_jenkinsfile.groovy.j2 | 2 +-
ci/jenkins/templates/gpu_jenkinsfile.groovy.j2 | 2 +-
5 files changed, 10 insertions(+), 9 deletions(-)
