1 / 8

AliRoot and AliEn B uild I ntegration and T esting S ystem

AliRoot and AliEn B uild I ntegration and T esting S ystem. Alina Grigoras alina.gabriela.grigoras@cern.ch. Have a current, up to date, installable binary image of AliEn and AliRoot for different architectures Automate the process of building AliEn components and of AliRoot

lobo
Download Presentation

AliRoot and AliEn B uild I ntegration and T esting S ystem

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AliRoot and AliEnBuild Integration and Testing System Alina Grigoras alina.gabriela.grigoras@cern.ch

  2. Have a current, up to date, installable binary image of AliEn and AliRoot for different architectures • Automate the process of building AliEn components and of AliRoot • 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 Purpose

  3. Currently we support for both AliEn and AliRoot • the following architectures: • SLC4 32 and 64 bits (soon to be discarded) • SLC5 32 and 64 bits • SLC4 Itanium • IntelMac 32 and 64 bits (32 soon to be discarded) • Ubuntu 64bits (for testing purpose) Supported architectures • AliEnBITS Web Interface Main Menu

  4. AliEn

  5. 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 WebServer • Purpose: fixing security issues raised by IT Security Dep. • Issues: affecting gridsite package, known to have building problems • Testing AliEn with the new packages • Adding features to the BuildServer itself • To be able to ignore at installation some packages, usually devel packages like ANT or JDK

  6. 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

  7. Future plans • Adding a gLite test environment, without installing gLite with AliEn (quite urgent) • Issues: installing gLite 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 AliEn 2-17.23 for 32bits and AliEn 2-17.30 for 64bits • Major cleaning of AliEn packages (somewhere in the future)

  8. AliRoot • Usual work: Building and registering to AliEn different tags of AliRoot • Current work: • Implementing an automatic email alert system • If AliRoot 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 AliEn, now it is done using an intermediate MonAlisa webpage

More Related