Mousius commented on PR #11809: URL: https://github.com/apache/tvm/pull/11809#issuecomment-1169685951
> [According to our Jenkinsfile](https://github.com/apache/tvm/blob/ce77d20c4615c655214d0bd38307813e539ba9a2/Jenkinsfile#L503-L511), both jobs that require ci_cpu and ci_qemu will run on the same target machines, so the expectation is that our Jenkins nodes will more commonly pull ci_cpu + ci_qemu in terms of storage Provided the images have the same initial layers (base image or copy paste both should work), the storage cost should be the same as it'll re-use the layers when pulling the containers - if a node already had `ci_cpu` it should have a bunch of layers it can re-use for `ci_micro`. > Creating a base image with common dependencies, would also generate a side problem, which is a time dependency to rebuild our images (we can't build all of them at the same time), and the need to create a generic label e.g. latest or last-successful for this base image to be picked up in the dependant images. I'd like to avoid this if possible. As far as I can tell we'd build `ci_base`, tag it with the same tag as the rest of the images and use that in the `FROM` of the subsequent images: ``` ARG TAG="latest" FROM tlcpackstaging/ci-base:${TAG} ``` Therefore, apart from a small network up/down to propagate the image, it should be a similar time to build as we have now? Sorry if I missed something here @leandron? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
