+1 for Docker, I can setup Docker with natted internet access, GCE even has an official docker VM. I am already using it on other projects. Perhaps we can flush this out in #iotivity on freenode? I'm pretty handy with docker and think that builds are a great use case for it. -Aric
On Wed, May 20, 2015 at 10:23 AM, Warburton, David <david.warburton at intel.com> wrote: > Docker (in my opinion) is a much more lightweight tool than vagrant for this > purpose. Vagrant may not even work on google cloud engine, since those > machines _are_ vms (and you can?t put a vm inside a vm). Docker containers > _do_ go into virtual machines very nicely though. > > The problem with Docker in the exact situation we currently have on the build > servers at LF is that those build servers are behind a firewall and need to > use an HTTP proxy to talk to the internet. This is a complication for Docker > and Docker doesn?t handle it very well. Docker expects all of the > configuration necessary to do the build to be in the Dockerfile, and doesn?t > allow build parameters or any enviornment variables to affect the build. > > If we want to use Docker, LF needs to move the build servers onto the > internet, or at least with NAT access to the internet (instead of none). > > Cheers, > David > >> On May 20, 2015, at 10:12 AM, Dieter, William R <william.r.dieter at >> intel.com> wrote: >> >> There are a number of tools these days for configuring virtual machines like >> Vagrant or Docker. The waymachine. The configuration files are generally >> small text files that can be checked into git. >> >> If you could use Docker (or Vagrant) to set up an Android and/or Tizen >> development environment locally. Jenkins to build and deploy Docker images >> from the repo, this would have several benefits: >> >> 1. You can do all the configuration in your local environment where it >> is easiest to work >> >> 2. The build machine will get an identical build environment to your >> local Docker environment >> >> 3. The environment will be version controlled and live in the repo, so >> different branches can have different build environments >> >> 4. Other developers can run the script to set up an equivalent build >> environment (this makes documentation easier) >> >> I did a sample Vagrant build environment for Linux early on and put the >> configuration files in <iotivity>/tools/vagrant. It has not been >> maintained, butinteresting place to start. Once you have Vagrant and >> VirtualBox installed, you can build and start the image with ?vagrant up?. >> >> Docker might be a more lightweight way to setup the build environment >> images. I am less familiar with it, but others may be able to help. >> >> With help from someone who knows the tools, getting an environment set up >> this way should not be a lot more work than just manually configuring a >> machine. long run, it will help accelerate development, because there will >> be canonical scripts new developers can use to boostrap their development >> environments. >> >> Bill. >> >> >> From: iotivity-infratructure-bounces at lists.iotivity.org >> [mailto:iotivity-infratructure-bounces at lists.iotivity.org] On Behalf Of >> ???(Uze Choi) >> Sent: Wednesday, May 20, 2015 4:03 AM >> To: Brian Warner >> Cc: iotivity-dev at lists.iotivity.org; iotivity-infratructure at >> lists.iotivity.org >> Subject: [Iotivity-infratructure] [Jenkins request] RE: RE: Build check >> request for every commit for Android and Tizen platform. >> >> Hi Brian (LF tech. manager), >> >> We are suffering from check whether build works well or not for Android and >> Tizen platforms. >> However, setting the environment does not seem to be easy as I described as >> below. >> Could you provide the solution to resolve it ASAP? Or any suggestion? >> >> BR, Uze Choi >> From: ???(Uze Choi) [mailto:uzchoi at samsung.com] >> Sent: Wednesday, May 20, 2015 2:03 PM >> To: 'Morrow, Joseph L'; 'heesung84.kim at samsung.com'; 'iotivity-dev at >> lists.iotivity.org'; '???' >> Cc: '???'; 'iotivity-infratructure at lists.iotivity.org' >> Subject: RE: RE: [Iotivity-infratructure] Build check request for every >> commit for Android and Tizen platform. >> >> Hi, Joey, >> >> Let me summarize the current situation. >> >> We need to enable the build checking and later the unit test checking for >> multi-platform. >> Currently Ubuntu build and unit testing is done thru Jenkins build. >> For the Android, Jenkins may not work.. Then who can enable to do it? >> Your comment seems to point out, we need to check the build output console >> from Jenkins log and request LF to do some remedy such as NDK configuration >> in the Jenkins server for each build break. >> As far as I know, we wasted so much time for Android build check in the >> Jenkins. >> For the Tizen, this is not easy task I think from scratch. I?m not sure they >> are able to do build for Tizen platform as of now. >> Every day we tested whether Tizen and Android platform build work or not >> which takes so much developer resource. >> What could be solution? In my opinion, let LF enable this build check for >> multi-platform. What is your opinion? >> >> BR, Uze Choi >> From: Morrow, Joseph L [mailto:joseph.l.morrow at intel.com] >> Sent: Wednesday, May 20, 2015 12:43 AM >> To: heesung84.kim at samsung.com; ???; iotivity-dev at lists.iotivity.org; >> ??? >> Cc: ???; iotivity-infratructure at lists.iotivity.org >> Subject: RE: RE: [Iotivity-infratructure] Build check request for every >> commit for Android and Tizen platform. >> >> Hi Kim Hee Sung, >> >> The build server is hosted by Linux Foundation. This means that the server >> is physically with Linux Foundation. wrt. giving direct access to the build >> server to anyone. AFAIK, the relationship of IoTivity with Linux Foun >> iotivity-helpdesk at rt.linuxfoundation.org) for all changes to the build >> server (to install the NDK and other things). This gives us a proper trail >> of all changes that is closely monitored. In any other case, breakages may >> easily occur without a trail (and therefore would be hard to fix). >> >> If you?re looking to make SConscript changes (ie. install the NDK to an End >> User?s machine automatically,all you need to do is simply edit the >> SConscripts in our repo). >> >> From what I can tell, there is no good reason to break our current >> arrangement with Linux Foundation. Ifscenario) for the Linux Foundation team >> to fix our builds if we broke the build in a serious way. This could hinder >> deadlines & releases. >> >> Please re-consider what you?re asking for. As for actually retrieving this >> access from Linux Foundation,I believe someone from Linux Foundation can >> chime in here. >> >> Thanks, >> >> Joey >> >> >> >> From: ??? [mailto:heesung84.kim at samsung.com] >> Sent: Monday, May 18, 2015 8:08 PM >> To: Morrow, Joseph L; ???; iotivity-dev at lists.iotivity.org; >> iotivity-helpdesk at rt.linuxfoundation.org; ??? >> Cc: ???; iotivity-infratructure at lists.iotivity.org >> Subject: Re: RE: [Iotivity-infratructure] Build check request for every >> commit for Android and Tizen platform. >> >> >> Hi Morrow, >> >> Thanks you for reply. I already know what you mean. >> >> In my opinion Uze Choi want to get authority for accessing the physical >> server. >> Because we want to install NDK or other things in the jenkins server >> directly. (for android build or tizen build) >> He told me android and tizen branches are not working well in the jenkins >> server. >> >> >> ? ?? ??. >> Regards, >> Kim hee sung. >> >> >> >> ------- Original Message ------- >> Sender : Morrow, Joseph L<joseph.l.morrow at intel.com> >> Date : 2015-05-18 22:51 (GMT+09:00) >> Title : RE: [Iotivity-infratructure] Build check request for every commit >> for Android and Tizen platform. >> >> Hi All, >> >> The script is found at the root of the IoTivity repository. Please see here: >> <IOTIVITY>/auto_build.sh >> >> To see how Jenkins calls this script (and to see partial build system >> configuration) see this publicly >> viewablehttps://build.iotivity.org/ci/job/Verify-IoTivity-Scons/configure >> >> To gain access to the above Jenkins page and to gain more insight into how >> the build machine is actuallyyou should do before he can actually take >> action. >> >> As you can see, there is plenty of accessibility.J >> >> Thanks, >> >> Joseph Morrow >> >> From: iotivity-infratructure-bounces at lists.iotivity.org >> [mailto:iotivity-infratructure-bounces at lists.iotivity.org] On Behalf Of >> ???(Uze Choi) >> Sent: Monday, May 18, 2015 2:38 AM >> To: iotivity-dev at lists.iotivity.org >> Cc: ???; iotivity-infratructure at lists.iotivity.org; ??? >> Subject: [Iotivity-infratructure] Build check request for every commit for >> Android and Tizen platform. >> >> For the Ubuntu, Jenkins build machine check whether build is successful or >> not. >> For the Android/Tizen platform, we also need to check by Jenkins? auto build >> script. >> >> Tim/Bernie/Raul/Joseph, there are some effort from yours, but still looks >> not finalized for Android build. >> Could you share the status and if special setting is needed, let?s escalate >> into LF >> For the Android build, Harish(h.marappa at samsung.com) is working for the >> primitive service. >> >> Brian(LF), due to lack of accessibility, we(Heesung.Kim) cannot look over >> the script and environment. >> Let?s us access over the build server. >> >> BR, Uze Choi >> <image001.gif> >> >> _______________________________________________ >> Iotivity-infratructure mailing list >> Iotivity-infratructure at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-infratructure > > _______________________________________________ > Iotivity-infratructure mailing list > Iotivity-infratructure at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-infratructure
