<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr">Hey guys,<div><br></div><div>I've prepared following repository to describe and help everybody understand how we can work with Github with respect to Docker Hub Automated Builds</div><div><br></div><div><a href="https://github.com/vpavlin/env-stacks-demo" target="_blank">https://github.com/vpavlin/env-stacks-demo</a><br data-mce-bogus="1"></div><div><br></div><div>Please read it, watch the video and let me know what do you miss, I'll add it. </div><div><br></div><div>I also added most of the WG members as contributors and will be happy to add you also to Docker Hub organization so that you can try to setup the builds - I will just need you account name on Docker Hub.</div><div><br></div><div>Cheers,</div><div>VaĊĦek<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Architect - Senior Software Engineer<br>Developer Experience<br>Brno, Czech Republic<br>Phone: +420 739 666 824<br></div></div></div></div>
</div></div></blockquote><div><br></div><div>Thanks for doing this, nice demo.<br></div><div><br></div><div>With regards to fedora-dockerfiles, I have different plans, though (not sure that they'll be implementable, but following weeks are going to reveal that :)).<br></div><div>So Scott accepted me as a comaintainer for fedora-dockerfiles and I realized that:</div><div>- doing the work there without CI is far from perfect; testing images by hand is both time consuming, not reproducible and not very reliable (only basic smoke tests are done)<br></div><div>- we should only put new images on dockerhub when they're properly tested<br></div><div>So what I'm going to try to do is:<br></div><div>- set up CI for fedora-dockerfiles, that will only test images altered in pull request/last push (because testing all images on every commit would be insanely wasteful, both resource wise and time wise)<br></div><div>- if the images pass the CI, they'll get pushed to dockerhub<br></div><div><br></div><div>I think dockerhub automatic building doesn't allow this workflow, so the images will have to be built and pushed by the CI (if that's possible). Another reason is that we want to push *exactly the image we built and tested*. If we built and tested the image and then told dockerhub to build it again on its own, we mightn't get the same image in some cases (e.g. new package gets to Fedora repos in the meantime, but also tons of other reasons).<br></div><div>Anyway, this is the plan that I created in my head and now I have to verify that it will actually be possible to implement it - I need to find out which CI would be the best etc. Hopefully, I'll be able to do that it in following 2 or 3 weeks. I'll be giving status updates on every meeting, so stay tuned :)<br></div><div><br></div><div>-- <br></div><div><span name="x"></span>Regards,<br>Slavek Kabrda<span name="x"></span><br></div></div></body></html>