1 / 19

Builds & Release status Marian.ZUREK@cern.ch on behalf of the Integration Team

Builds & Release status Marian.ZUREK@cern.ch on behalf of the Integration Team. JRA1 All-hands-meeting, Brno 21.VI.2004. www.eu-egee.org. EGEE is a project funded by the European Union under contract IST-2003-508833. Contents. Build Infrastructure Builds Repository, updates

rbraithwaite
Download Presentation

Builds & Release status Marian.ZUREK@cern.ch on behalf of the Integration Team

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. Builds & Release statusMarian.ZUREK@cern.chon behalf of theIntegration Team JRA1 All-hands-meeting, Brno 21.VI.2004 www.eu-egee.org EGEE is a project funded by the European Union under contract IST-2003-508833

  2. Contents • Build Infrastructure • Builds • Repository, updates • Integration testbed • CruiseControl • Release MGMT • Releases • Current tags • Last builds • How we continue • Training session • Future

  3. Builds • CONTINUOUS build (ix86: Linux+WinXP) • On glite_branch_1_2_0 • On HEAD • NIGHTLY build (ix86: Linux+WinXP) • On glite_branch_1_2_0 • ia64 builds(SL Linux) • External dependencies already available (recompiled) • Java OutOfMemory issue when running inside the CC • New platforms (AIX, PPC, …) • generic mechanism for multi-platform builds under studies

  4. Builds • INTEGRATION aka “weekly” builds • 15 subsystems, 209 modules (167 during Padova) • Manual process • src, tar.gz, RPMS, quattor templates • Installation scripts (per deployment module) • Release notes, Documentation, Configuration scripts • “stage” area provided as a tarball (all the libraries present) • RedHat “migration” • CERN licensing: WS to AS move • Transparent to buid system users

  5. APT repository • Public • http://glite.web.cern.ch/glite/packages/APT.asp • Internal for the tests

  6. Quick fixes / APT updates • Announced via glite-announce@cern.ch • Deployment scripts updated on the gLite web page: • http://glite.web.cern.ch/glite/packages/R1.1/QFs/ • New RPMs available on the public APT repository (APT source string): • rpm http://glitesoft.cern.ch/EGEE/gLite/APT/R1.1 rhel30 externals Release1.1 • update directory in the future, currently • apt-get updatefollowed byapt-get upgrade • tomcat5issue - fixed in “-8” version (manual uninstall needed for version “-6” and “-7” upgrades: RPM %post install policy) • When/how to apply the Qfes • directly via deployment scripts • via APT

  7. Integration testbed • Automatic installation of integrated software for configuration testing • Currently 7+ machines running SLC3/RHELv3 (+updates) • Always start from the CLEAN REFERENCE OS installation • Scratch-return-to original configuration within minutes • Smoke tests in collaboration with the testing team • Repository • gLite Web server for now • quattor software repository in the future • Quattor templates being developed • We may use in the future to automate/facilitate the installation and configuration testing

  8. Build/CruiseControl • Current issues (we put lots of effort to solve them) • version properties = version.properties + build.number • merges/copies from various places => tagging failing • Fixed - please pay attention to the new files content • Broken NIGHTLY/CONT. builds • Faulty tags, non-existing/missing modules • Sometimes we need to fix the configuration, dependency problems • Working on the inter-module dependencies (across the subsystems). • CVS performance degradation (disk changes, NW glitches) • Automated external dependencies generation

  9. Release Management • Based on CVS tags • Close contact with the cluster release managers • Please tag your components. You may also want to tag the subsystems, but we can take care of subsystems for you. • Please send your tags on time • A tag explicitly communicated by the release manager • The same tag used in the previous integration build, if no tag is explicitly communicated • The latest successfully built tag on the nightly build server, if no tag is explicitly communicated and no previous integration build tag is available • The component is excluded from the build if none of the previous tags is available

  10. Release Management • Baseline • Snapshot of the code in CVS not yet completely finished • Release • Snapshot … completely finished and functional; i.e. ready for integration and testing • Branch • Useful for parallel development of the component taken from the given baseline or release tag for the bug fixes, new functionality, experiments. In the later stage could be merged to into the main dev. branch, persist as variants or die …

  11. Where to commit my code??? • Release v1.2 • in branch: glite_branch_1_2_0 • New functionality • in HEAD • Create a new branch • cvs tag -b <my-branch-name> • As simple as “click” with eclipse

  12. Release Management (branches)

  13. Release Management (tagging) • Tagging • Using the prepared ant targets (please) • cd <subsystem-dir> • ant baseline_tag or ant release_tagorant branch_tag • Manual • Please make sure you are creating the properly formatted tag (should contain the build number) e.g. glite-ce-monitor_B_1_4_22_76 (BASELINE), glite-ce_R_1_2_5 (RELEASE) • For the tagging make sure you update accordingly the <component-dir>/project/version.properties • You are free to use your favourite tag format for your “private” use, but please stick to our standards as much as possible to make life easier

  14. Releases • R1.0 : Mar Apr 05 2005 • R1.1 : Thu May 12 2005 • (internal-SC3) R1.1.1 : Mon May 30 2005 • (internal-SC3) R1.1.2 : Tue Jun 14 2005 • R1.2 : beginning of July

  15. Release R1.2 • Current tags org.glite.deployment.version= glite-deployment_branch_1_2_0 org.glite.testsuites.version = glite-testsuites_R_1_2_1 org.glite.alien.version = glite-alien_B_2_0_0_200 org.glite.ce.version = glite-ce_R_1_2_1 org.glite.data.version = glite-data_R_1_3_1 org.glite.lb.version = glite-lb_R_1_0_3 org.glite.rgma.version = glite-rgma_R_4_1_6 org.glite.security.version = glite-security_R_1_2_4 org.glite.service-discovery.version = glite-service-discovery_R_2_0_2 org.glite.templates-latex-style.version = glite-templates-latex-style_R_1_0_1 org.glite.wms-ui.version = glite-wms-ui_R_1_0_6 org.glite.wms-utils.version = glite-wms-utils_R_1_0_3 org.glite.wms.version = glite-wms_R_1_0_5 org.gridsite.core.version = gridsite-core_R_1_1_10 org.glite.dgas.version = glite-dgas_B_1_0_0_161 org.glite.version = glite_branch_1_2_0_RC2

  16. Release v1.2 • More stability needed • Delays have a direct impact on the integration/testing “train” • Min. TWO WEEKS needed to integrate & test • Tested tags, not only compiling code • Fixes in the appropriate branches (R1.0, R1.1, R1.2…) • Modules for SCX == modules (R1.?, 2.??)

  17. gLite Tutorial • 16-17 June 2005 at CERN • ±1.5 day session • Target: system administrators • 25+ participants • “From base” exercises • Highly appreciated • Valuable feedback gathered

  18. Future • Keep going • Xen investigation • Operating prototype testbed

  19. Q&A Discussion

More Related