You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2020/04/25 06:49:09 UTC

[GitHub] [trafficcontrol] zrhoffman commented on pull request #4639: Use prebuilt images to build Traffic Control components

zrhoffman commented on pull request #4639:
URL: https://github.com/apache/trafficcontrol/pull/4639#issuecomment-619331673


   Okay, the Docker Hub repositories should be little more usable now.
   
   For the tags listed above, Docker Hub has images for releases from `RELEASE-2.0.0` through `RELEASE-4.1.0-RC0` (built locally and pushed after waiting the full 1 week timeout for Docker Hub's queue of images to build. It probably didn't finish because that was 7749 separate builds).
   
   Removed release candidate tags that are not well-defined at all times (examples for RC tag `RELEASE-4.0.0-RC2`: `RELEASE-4.0-RC2`, `RELEASE-4-RC2`, `RELEASE-RC2`, `4.0-RC2`, `4-RC2`, `RC2`).
   
   Also generated a list of tags for each repo that link to the Dockerfiles. The top of `trafficcontrol/traffic_monitor_builder`'s readme, for example:
   
   > ## Supported tags and respective `Dockerfile` links
   > * [master](https://github.com/apache/trafficcontrol/blob/master/infrastructure/docker/build/Dockerfile-traffic_monitor)
   > * [RELEASE-4.1.0-RC0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4.1.0-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4.1-RC0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4.1-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4-RC0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4.1.0-RC0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4.1.0-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4.1-RC0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4.1-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4-RC0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4-RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RC](https://github.com/apache/trafficcontrol/blob/RELEASE-4.1.0-RC0/infrastructure/docker/build/Dockerfile-traffic_monitor)
   > * [RELEASE-4.0.0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4.0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-4](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4.0.0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4.0](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [4](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [latest](https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/infrastructure/docker/build/Dockerfile-traffic_monitor)
   > * [RELEASE-3.1.0](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-3.1](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE-3](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [RELEASE](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [3.1.0](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [3.1](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor), [3](https://github.com/apache/trafficcontrol/blob/RELEASE-3.1.0/infrastructure/docker/build/Dockerfile-traffic_monitor)
   
   Updating the tags in the READMEs is something that Docker Hub doesn't do itself, so maybe we could write a Jenkins job to update them.
   
   Repos:
   
   * https://hub.docker.com/r/trafficcontrol/docs_builder
   * https://hub.docker.com/r/trafficcontrol/grove_builder
   * https://hub.docker.com/r/trafficcontrol/grovetccfg_builder
   * https://hub.docker.com/r/trafficcontrol/source_tarballer
   * https://hub.docker.com/r/trafficcontrol/traffic_monitor_builder
   * https://hub.docker.com/r/trafficcontrol/traffic_ops_builder
   * https://hub.docker.com/r/trafficcontrol/traffic_portal_builder
   * https://hub.docker.com/r/trafficcontrol/traffic_router_builder
   * https://hub.docker.com/r/trafficcontrol/traffic_stats_builder
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org