<div dir="ltr">Is there anything preventing us from using the hooks in github to automate this? (or is that what you're proposing?)<div><br></div><div>I would expect the following to be sufficient (and fully automatable via both docker hub and quay):</div><div>master => latest</div><div>{git release tags} => image tag</div><div><br></div><div>-John</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 14, 2018 at 6:27 AM Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Aug 14, 2018 at 02:09:59PM +0530, Nigel Babu wrote:<br>
> Hello folks,<br>
> <br>
> Do we know who's the admin of the Gluster organization on Docker hub? I'd<br>
> like to be added to the org so I can set up nightly builds for all the<br>
> GCS-related containers.<br>
<br>
Nice! Which containers are these? The ones from the gluster-containers<br>
repository on GitHub?<br>
<br>
I was looking for this as well, but also for the team that exists on<br>
<a href="http://quay.io" rel="noreferrer" target="_blank">quay.io</a>.<br>
<br>
There has been a request to keep clearly identifyable versioning for our<br>
containers. It is something I wan to look at, but have not had the time<br>
to do so. A description on which contaners we have, where the sources<br>
are kept, base OS and possible branches/versions would be needed (maybe<br>
more). If this is documented somewhere, a pointer to it would be great.<br>
Otherwise I'll need assistence on figuring out what the current state<br>
is.<br>
<br>
Thanks,<br>
Niels<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div>