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 viewable page: 
https://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 actually configured, please contact Aric Gardner from Linux 
Foundation. I have found the best way to start a work item is to draft an email 
(which is then converted to a ticket on LF?s side) and send it to 
'iotivity-helpdesk at rt.linuxfoundation.org'. Aric Gardner is usually the 
person to pick these items up. If there is more prep work on your side to do, 
he is pretty good at letting you know what is able to do and what you should do 
before he can actually take action.

As you can see, there is plenty of accessibility. :)

Thanks,

Joseph Morrow

From: iotivity-infratructure-bounces at lists.iotivity.org 
[mailto:[email protected]] 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<mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150518/2d69817b/attachment.html>

Reply via email to