[Hawkular-dev] Hawkular image and the docker hub registry

[Matt Wringe]

On 20/05/15 09:17 AM, Viet Nguyen wrote:
> Matt,
>
>
> I put together a diagram awhile back:
>
> https://docs.google.com/presentation/d/14zqOHOvXAB4uN7W_fWOub3ZD6txiS_Vp9cjUNIlj2yQ/edit?usp=sharing
>
>
> Kettle build hook:
>
> https://github.com/hawkular/hawkular/blob/master/.travis.yml#L20

Yes, I have already seen that. If I were to use that approach, I still 
need access to the CI server which I don't current have (or need someone 
to help set that up if I am not allowed access).

The current approach is not something that I find works well for the 
docker containers I am dealing with. I would prefer to build the docker 
images in our CI and then push the binary to the docker repo, rather 
than have the images build using the docker hub automated build system.

But I think setting it up initially using the automated build will at 
least get us something up and running more quickly than trying to figure 
out how to build (and mange) the docker builds within our CI.

- Matt

>
>
> ----- Original Message -----
> From: "Matt Wringe" <mwringe at redhat.com>
> To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Sent: Wednesday, May 20, 2015 6:19:40 AM
> Subject: [Hawkular-dev] Hawkular image and the docker hub registry
>
> There are a few images we should push out under the 'hawkular'
> organization account on docker hub:
>
> - hawkular-metrics
> - hawkular-cassandra
> - hawkular-heapster*
>
> *: only until https://github.com/GoogleCloudPlatform/heapster/pull/284
> is closed
>
> If there are no objections, I will create those images soon under the
> 'hawkular' account.
>
> Initially, it will probably set it up as an automated docker hub build
> (since we can get it up and running very quickly). But we should really
> change it so that we build the images ourselves as part of the CI build
> and push the images out to docker hub. This will keep things more inline
> with that the kubernetes application will be expecting and prevent us
> from manually having to update the docker configurations when the
> versions change.
>
> I have no idea how our current CI works, so if someone could help me
> here that we would be great. I am assuming building the docker images
> there will be a simple task.
>
> Thanks,
>
> Matt Wringe
>
> _______________________________________________
> 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