camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: R: Re: Using docker for Camel CI/CD
Date Wed, 22 Jul 2015 04:16:06 GMT
Hi

No I dont think that its a requirement, its just what people often
have installed and used for building.

I think open jdk should be able to build also.

On Wed, Jul 22, 2015 at 5:07 AM, Mark Webb <elihusmails@gmail.com> wrote:
> While it does not explicitly state on the page:
>
> http://camel.apache.org/building.html
>
> Are all the Camel release builders using Oracle Java?  This may make
> creating a Docker image using Oracle Java a little tricky.
>
>
>
> On Tue, Jul 21, 2015 at 10:52 AM, Andrew Block <andy.block@gmail.com> wrote:
>
>> +1 for Docker Hub. It will allow for automated builds from a Git source
>> and is the default registry for Docker users
>>
>> --
>> Andrew Block
>>
>> On July 21, 2015 at 9:02:40 AM, Andrea Cosentino
>> (ancosen1985@yahoo.com.invalid) wrote:
>>
>> I think there is no problem using dockerhub.
>>
>>
>> Andrea
>>
>> Inviato da Yahoo Mail su Android
>>
>> Da:"Mark Webb" <elihusmails@gmail.com>
>> Data:mar, 21 lug, 2015 alle 15:56
>> Oggetto:Re: Using docker for Camel CI/CD
>>
>> I plan on using Docker Hub (hub.docker.com) to store any images that I
>> create.  Does this sound OK.  I don't expect any issues with
>> licensing..etc.
>>
>>
>>
>> On Mon, Jul 20, 2015 at 4:39 PM, Mark Webb <elihusmails@gmail.com> wrote:
>>
>> > Dan,
>> >
>> > I agree with you 100%.  I will add this to the list.
>> >
>> > Thanks,
>> > Mark
>> >
>> >
>> > On Mon, Jul 20, 2015 at 3:51 PM, Daniel Kulp <dkulp@apache.org> wrote:
>> >
>> >> My main requirement would be that docker images for any of the below
>> >> actions are there for convenience for developers that may want to use
>> them,
>> >> but should not be REQUIRED for any of those actions.  For those of us
>> >> that have release environments already setup using the normal
>> >> “release:prepare/perform” steps should be able to continue using that
>> >> setup.  Developers should NOT need to have docker setup or even
>> installed
>> >> to do any normal day to day activities.
>> >>
>> >> Dan
>> >>
>> >>
>> >>
>> >> > On Jul 20, 2015, at 2:32 PM, Mark Webb <elihusmails@gmail.com>
wrote:
>> >> >
>> >> > I am starting a new thread as a follow-up to the earlier discussion
on
>> >> this
>> >> > mailing list.  I would like to get opinions and some direction as we
>> >> move
>> >> > forward on migrating the Apache Camel build process with Docker.
>> Based
>> >> on
>> >> > what I've gathered so far, we can use Docker to:
>> >> >
>> >> > 1. Have a common baseline in which to build Apache Camel
>> >> > 2. Put together a variety of environments in which to perform either
>> >> unit
>> >> > tests or integration tests.
>> >> > 2a. Different JDK's
>> >> > 2b. Different versions of applications/systems that Apache Camel has
>> >> > connectors for.
>> >> > 3. Allow for a commonly defined tool chain to build Apache Camel.
>> >> >
>> >> > What are your thoughts on how we should move forward?
>> >> >
>> >> > ..Mark
>> >>
>> >> --
>> >> Daniel Kulp
>> >> dkulp@apache.org - http://dankulp.com/blog
>> >> Talend Community Coder - http://coders.talend.com
>> >>
>> >>
>> >
>>
>>



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition: http://www.manning.com/ibsen2

Mime
View raw message