Ali Root and Ali En Build Integration and
Ali. Root and Ali. En Build Integration and Testing System Alina Grigoras alina. gabriela. grigoras@cern. ch http: //pcalibuildintel. cern. ch: 8888/8889
Purpose Have a current, up to date, installable binary image of Ali. En and Ali. Root for different architectures Automate the process of building Ali. En components and of Ali. Root Better understanding of the dependencies between packages Perform functional and unit tests at build time and receive alerts immediately Web interface that allows the monitoring of the build status and remote access to logs http: //pcalibuildintel. cern. ch: 8888/8889
Supported architectures Currently we support for both Ali. En and Ali. Root the following architectures: SLC 4 32 and 64 bits (soon to be discarded) SLC 5 32 and 64 bits SLC 4 Itanium Intel. Mac 32 and 64 bits (32 soon to be discarded) Ubuntu 64 bits (for testing purpose) Ali. En. BITS Web Interface Main Menu http: //pcalibuildintel. cern. ch: 8888/8889
Ali. En http: //pcalibuildintel. cern. ch: 8888/8889
Current work • Updating key packages: • Globus Toolkit • Purpose: • Fixing a bug related to the recompilation of Gapi • having only one version of openssl • Issues: • Affecting a big number of packages including Gapi • Updating packages • Patching packages • Needs extra packages as requirements (JDK and ANT) • Apache Web. Server • Purpose: fixing security issues raised by IT Security Dep. • Issues: affecting gridsite package, known to have building problems • Testing Ali. En with the new packages • Adding features to the Build. Server itself • To be able to ignore at installation some packages, usually devel packages like ANT or JDK http: //pcalibuildintel. cern. ch: 8888/8889
Current work • All the changes from previous slide must be applied and tested on all platforms • Issues: • Some packages are really old and they are not supported anymore • Rebuilding a distribution takes ~a couple of hours thus each iteration is slow • Problems are really difficult to spot • Packages that don't have a clear building and installation script • Because of the big number of packages and dependencies one change in a package can trigger a whole chain of problems • Some packages are not supported at all for some platforms, usually for Mac http: //pcalibuildintel. cern. ch: 8888/8889
Future plans • Adding a g. Lite test environment, without installing g. Lite with Ali. En (quite urgent) • Issues: installing g. Lite on all build servers independent of the build and testing process, certificates etc • Synchronizing the build number between different platforms (quite urgent) • You can have Ali. En 2 -17. 23 for 32 bits and Ali. En 2 -17. 30 for 64 bits • Major cleaning of Ali. En packages (somewhere in the future) http: //pcalibuildintel. cern. ch: 8888/8889
Ali. Root • Usual work: Building and registering to Ali. En different tags of Ali. Root • Current work: • Implementing an automatic email alert system • If Ali. Root fails, check where it failed and email the responsible persons about it • This applies only to the trunk, that is build every night • Future plans : automatically register packages to Ali. En, now it is done using an intermediate Mon. Alisa webpage http: //pcalibuildintel. cern. ch: 8888/8889
- Slides: 8