[Hawkular-dev] http://www.jboss.org/docker/

[Matt Wringe]

On 09/06/15 09:34 AM, Thomas Heute wrote:
>
> On 06/09/2015 03:29 PM, Matt Wringe wrote:
>> I believe what is happening here is that they are using the Docker Hub
>> automated build system with that particular github repo.
>>
>> This will be similar to the same setup we have right now with docker
>> hub. I don't know who in this case sets up things like build hooks, if
>> its the jboss-dockerfiles account holder of if we also have some
>> permissions granted. We do not want to have to update a file in that
>> github account everytime we build a new snaphot :) So we need to setup
>> the automation like we currently have.
> That particular repo is for tagged release AFAIK.
> This is what is promoted on http://www.jboss.org/docker/

Ah, ok, so it works a bit better with tagged releases. But when what 
happens with our current snapshot releases? I guess we still need to 
keep them under our Hawkular account, which means we have multiple 
docker hub accounts hosting similar images?

>
> I got confirmation that the only thing we have to do is push a change on
> https://github.com/jboss-dockerfiles/hawkular and images will end up here:
> https://registry.hub.docker.com/repos/jboss/
>
> If the FROM changes, it will also rebuild our image AFAIK
>
> Thomas
>
>> The docker hub automated builds are not something I think we should be
>> looking into at all. It lacks basic features and doesn't work nicely
>> with normal workflows.
>>
>> We will not be able to:
>>
>> - build our own docker images
>>
>> - tag particular images
>>
>> - run tests on the images before they are published (publishing first
>> and then being able to run tests is a backwards approach)
>>
>> - automatically update versions when a new release happens (this
>> requires a bunch of extra manual steps in multiple locations)
>>
>> - keep things synchronized with kubernetes applications
>>
>> - keep most of the docker build artifacts, configurations and tests in
>> the same place.
>>
>> - have an nice developer experience.
>>
>> For the all-in-one Hawkular I guess since someone else is looking into
>> that I don't have to worry too much about it, but for our metrics
>> containers I do not want them using the automated build approach.
>>
>> - Matt
>>
>> On 09/06/15 07:48 AM, Thomas Heute wrote:
>>> On 06/09/2015 01:24 PM, Heiko W.Rupp wrote:
>>>> On 9 Jun 2015, at 13:13, Thomas Heute wrote:
>>>>
>>>>> I just requested to be added to http://www.jboss.org/docker/
>>>>> This is the docker source that I propose and should move to the official
>>>>> GitHub Repo:
>>>>> https://github.com/theute/hawkular-docker-jbossorg/
>>>> Sorry, Hawkular.org does not accept readme.md files :->
>>> It follows the https://github.com/jboss-dockerfiles/hawkular standards :)
>>>
>>>> On a more serious note: the main question is probably
>>>> how do we build it from the specific tag - just via mvn docker:build
>>>> and then upload to dockerhub?
>>> AFAIK, I push to https://github.com/jboss-dockerfiles/hawkular and the
>>> rest is handled
>>>
>>>> Do I understand correctly, that those images are released together
>>>> with the respective .zip/.tgz releases coming from a tag / milestone version?
>>> Right, that's the idea. See other projects:
>>> https://github.com/jboss-dockerfiles
>>>
>>> Thomas
>>>
>>>
>>>>       Heiko
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev