Hi, There has been a lot of confusion and changes around this topic and I want to clear things up going forward, so we do not waste any of our time. What I understand from all the disparate discussions around this topic is:
1. We will not do alpine for E0 release on arm, we are targeting E1/E2 2. For the Functest-core image we will have 1 Dockerfile for x86, and a patch for arm that overrides this Dockerfile; from this file we will create one Functest-core image and the architecture will be mentioned in its tag 3. The subsequent images (Functest-healthcheck, Functest-smoke, etc) will be based on the previously built Functest-core image. We will do a manifest to choose the correct Functest-core image based on its tag. These dependent images will also have its arch in the tag. 4. The problem we are facing now is how to make sure that for 1 build, the Functest-core image always get built before the other ones. For x86 that is now done with a workaround directly in dockerhub. The target is to do it with Jenkins jobs builders, considering image dependencies. Is this the approach we are all agreeing on? Thanks, Cristina
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
