Autobuilds and daily updates
Posted by Steve Revill Tue, 21 Jul 2009 23:31:00 GMT
RISC OS Open have finished implementing a system which automatically rebuilds the source code tarballs on the web site.
We have also automated the process of testing various builds and uploading the results to our web site – assuming the builds don’t fail!
Over time, we will be extending this process to build more and more components straight from our source repository so you can be sure that the versions of software that you download from our web site are reasonably up-to-date.
More information
At present, we are performing the following builds as autobuilds:
- Tungsten and TungstenDev (IYONIX ROM images)
- OMAP3Dev (Beagleboard ROM image)
- IOMDHALDev (A7000 and RiscPC ROM image)
- BuildHost, BuildHostDev, CToolsDev (ROOL-internal)
We will soon be extending these build processes to include updating the softload tool archives and pre-built modules and applications.
Note to buildmasters
Actually performing each build usually takes around 30 minutes to an hour of IYONIX build machine time (assuming certain technical considerations). As such, we’ll probably only repeat the process of performing all of the builds roughly once per week.
If you are interested in setting up as an autobuild machine-time donor (i.e. donate some build machine time to perform regular autobuilds for us) then get in touch here. You will need the official C/C++ Tools and ideally an IYONIX for this.
Also note: each build can have associated email addresses (a build master and a CC list). These people are sent an email notification if and when a build fails. ROOL will be shortly contacting regular contributors to various builds
to ask if they want to be the nominated build master or on the CC list – because it’s more likely that build failures will be caused by changes they’ve contributed, so it’s useful for them to know about it.
