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 <elihusma...@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 dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
