Docker Hub Automated Builds Demo Draft

Vaclav Pavlin vpavlin at redhat.com
Thu Oct 1 09:50:04 UTC 2015


Oh, cool, sounds great, I'm happy to help you with this effort if you
want/need:)

Vašek

On Thu, Oct 1, 2015 at 10:39 AM, Bohuslav Kabrda <slavek at redhat.com> wrote:

> ------------------------------
>
> Hey guys,
>
> I've prepared following repository to describe and help everybody
> understand how we can work with Github with respect to Docker Hub Automated
> Builds
>
> https://github.com/vpavlin/env-stacks-demo
>
> Please read it, watch the video and let me know what do you miss, I'll add
> it.
>
> 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.
>
> Cheers,
> Vašek
>
> --
> Architect - Senior Software Engineer
> Developer Experience
> Brno, Czech Republic
> Phone: +420 739 666 824
>
>
> Thanks for doing this, nice demo.
>
> 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 :)).
> So Scott accepted me as a comaintainer for fedora-dockerfiles and I
> realized that:
> - 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)
> - we should only put new images on dockerhub when they're properly tested
> So what I'm going to try to do is:
> - 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)
> - if the images pass the CI, they'll get pushed to dockerhub
>
> 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).
> 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 :)
>
> --
> Regards,
> Slavek Kabrda
>
> _______________________________________________
> env-and-stacks mailing list
> env-and-stacks at lists.fedoraproject.org
> https://lists.fedoraproject.org/mailman/listinfo/env-and-stacks
>
>


-- 
Architect - Senior Software Engineer
Developer Experience
Brno, Czech Republic
Phone: +420 739 666 824
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/env-and-stacks/attachments/20151001/40f1def9/attachment.html>


More information about the env-and-stacks mailing list