Hi, It looks nice!
Here are some comments. The most important comment I have is the ability to run docker builds for patches as part of verify jobs and post feedback to OPNFV Gerrit. If we go this path, we will have pre-merge builds done on our machines and post-merge builds done on docker hub, which will result in at least same amount of maintenance effort if not more. Also things might result differently due to having 2 different environments where the builds are done. The other comments are the synching, the no of concurrent builds, and the visibility. The synching will definitely slow things down as we need to wait for it to be done. This might be annoying when a crucial bugfix needs to be merged/built. The other possibility is if/when we have issues with synching which might further delay builds. The no of concurrent builds will cause limitations time to time and some builds will have to wait in the dockerhub queue. And finally there will be 2 places to look at for the builds/logs for different things; OPNFV jenkins and docker hub. Also, the synching and concurrent build limit will contribute to the increase in time to get feedback as well. Time to get feedback will increase to time to synch + possible queueing from direct/post-merge triggered builds on our Jenkins. Ps. I will be one of the happy persons if we move to docker hub so I can get rid of maintaining build servers. But I also need to highlight some of the limitations if we do this. /Fatih On 19 Jul 2017, at 15:30, Jose Lausuch <jose.laus...@ericsson.com> wrote: Hi, Following up on the discussion about how to build our Docker images, I started a trial with Trevor Bramwell with automated builds on Dockerhub for some of the new Functest Docker images: https://hub.docker.com/r/opnfv/functest-core/builds/ https://hub.docker.com/r/opnfv/functest-smoke/builds/ https://hub.docker.com/r/opnfv/functest-healthcheck/builds/ It triggers a build after the corresponding repository in Github (mirror) has new code. Basically, whenever a new patch is merged on OPNFV gerrit and synched with Github. There is currently a small limitation in the OPNFV Dockerhub account: it can build only 1 image at a time, but we can change that up to 5 or more parallel builds by requesting an account upgrade to LF. You can see the pricing plan here: https://hub.docker.com/account/billing-plans/ We could use this to avoid load on our build servers, use them for something else and of course stop maintaining docker builds in OPNFV. I would like to know your opinion on that. Thanks, Jose _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
