[Dev] Automated building of external/internall tarballs

[Heikki Toivonen]

We now have six Tinderbox clients operational at OSAF, two for each 
major platform. For each platform we have one client doing 'make 
install' and one doing 'full build'.

We have also enhanced the 'full build' Tinderbox clients to upload the
tarballs they produce to a public staging area. Along with this change 
we also have a new web tool 
(http://builds.osafoundation.org/cgi-bin/tbhelp.cgi) that let's you
view the list of tarballs available and copy them to the area used by 
'make install' builds. All of this without needing to login to the build 
machines.

The tool will not overwrite files. This means that when you update an 
external/internal system and want to use this tool to copy the tarballs, 
you must also change the version/relver in its Makefile (this will 
produce a tarball with different name).

The tool requires a username and password. If you are making changes in 
external/internal, you need to send me username and password hash - see 
instructions here: 
http://lxr.osafoundation.org/source/hardhat/tbhelp.cgi#059

What all this means is that if you are making changes in internal or 
external, you can check in your changes and let the Tinderbox clients do 
the tedious work of compiling the changes on all platforms - you just 
need to confirm the results and use the web tool to copy the tarballs. 
Note: you should still do your best to make sure your changes compile on 
all platforms etc.

There are two caveats (these still need to be implemented). 1) If any 
part of the 'full build' cycle fails (build, distribution building 
process, unit tests), then the tarballs will not be uploaded. 2) You 
need access to builds.o11n.org to upload external source tarballs and 
md5sums.


'make install' way is the most important build. You should never break it.

It may be ok to break the 'full build' temporarily. As a rule of thumb,
you should let others know when you intend to break the 'full build', 
and the build should not be broken for more than 24 hours at a time. 
Example when it is ok to break the 'full build': changing external or 
internal will break distribution building process or unit tests until 
they are changed - but they cannot be changed until the 
external/internal tarballs are available for the 'make install' build.

-- 
   Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20041216/d50ee4ec/signature.bin