[ci][docker] Fall back to tlcpackstaging if images don't exist by driazati · Pull Request #11775 · apache/tvm

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

driazati · 2022-06-18T00:11:58Z

See #11768. This adds a script to check if Docker images exist in tlcpack and switch to tlcpackstaging if not (the tags must match though). There is also a feature flag for this in jenkins in the DETERMINE_DOCKER_IMAGES env variable (which must be set to yes for this change to work)

cc @Mousius @areusch

See #11768

driazati · 2022-06-22T21:30:23Z

@tvm-bot rerun

areusch · 2022-06-22T23:00:43Z

+ )
+ parser.add_argument(
+ "--base-dir",
+ default=".docker-image-names",


should this be relative to repo root?

in tests it needs to be off in a random tempdir (and that's the only place this is really used)

github-actions · 2022-06-22T23:12:34Z

Built docs for commit 9240ff20484c07f896cb4a3d6ed0cfb9be3b5a79 can be found here.

This uses #11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

…e#11775) See apache#11768. This adds a script to check if Docker images exist in `tlcpack` and switch to `tlcpackstaging` if not (the tags must match though). There is also a feature flag for this in jenkins in the `DETERMINE_DOCKER_IMAGES` env variable (which must be set to `yes` for this change to work)

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See #11768, this PR changes the deploy workflow so that after a successful build with fallback images (see #11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This uses apache#11775 to make local builds work if they're run in the meantime before CI tags over a new image to tlcpack Co-authored-by: driazati <driazati@users.noreply.github.com>

See apache#11768, this PR changes the deploy workflow so that after a successful build with fallback images (see apache#11775), they get moved over to tlcpack automatically. Since the images are moving repositories we can't just rename the blobs in docker, so there needs to be a full `pull -> tag -> push` for each image

This was referenced Jun 18, 2022
[docker] Implement Docker image automated updates #11768
Closed
[ci][docker] Send a PR to bump the Docker images nightly #11813
Merged
[ci][docker] Tag tlcpackstaging images to tlcpack #11832
Merged

[ci][docker] Fall back to tlcpackstaging if images don't exist
9240ff2
See #11768

driazati marked this pull request as ready for review June 22, 2022 17:08

areusch approved these changes Jun 22, 2022
View reviewed changes

driazati merged commit 6660e27 into apache:mainJun 23, 2022

driazati mentioned this pull request Jun 30, 2022
[docker] Fall back to tlcpackstaging in bash.sh #11976
Merged

driazati mentioned this pull request Jul 14, 2022
TVM v0.9.0.rc0 Release Candidate Notes #12102
Closed