1 / 17

Release BETA Release BETA Build Plan Geneva - 1 March 2007

Release BETA Release BETA Build Plan Geneva - 1 March 2007. Paolo Fabriani paolo.fabriani@eng.it. Summary. Release Beta Numbers Analysis of component dependencies Integration configurations: a proposal Expected times for build cycles Build scheduling and execution

gari
Télécharger la présentation

Release BETA Release BETA Build Plan Geneva - 1 March 2007

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. Release BETARelease BETA Build PlanGeneva - 1 March 2007 Paolo Fabriani paolo.fabriani@eng.it

  2. Summary • Release Beta Numbers • Analysis of component dependencies • Integration configurations: a proposal • Expected times for build cycles • Build scheduling and execution • ETICS usage & infrastructure needs • Naming conventions update Release BETA Meeting - Geneva, 1-2 March 2007

  3. Release BETA Numbers • From ETICS • 20 Subsystems • More than 200 Components • Services, Stubs, API, Service Archives • From Savane • 158 Components • 75 Services • 49 Libraries • 34 Portlets Release BETA Meeting - Geneva, 1-2 March 2007

  4. Release BETA Numbers Release BETA Meeting - Geneva, 1-2 March 2007

  5. Application Layer (5) Personalisation (5) Feat Ext PDes (4) gLite DIR(4) Search (4) Cont Sec POpt(3) PExec(3) Index (4) Annotation CM(2) MM(3) PRes (2) DVOS Keeper BMM VDL DIS Dependency Analysis Release BETA Meeting - Geneva, 1-2 March 2007

  6. Dependency Analysis Application Layer (5) Personalisation (5) Feat Ext PDes (4) gLite Cont Sec DIR(4) Search (4) POpt(3) PExec(3) Index (4) Annotation CM(2) MM(3) PRes (2) DVOS Keeper BMM VDL DIS Release BETA Meeting - Geneva, 1-2 March 2007

  7. Dependency Analysis Application Layer (5) Personalisation (5) Feat Ext PDes (4) gLite Cont Sec DIR(4) Search (4) POpt(3) PExec(3) Index (4) Annotation CM(2) MM(3) PRes (2) DVOS Keeper BMM VDL DIS Release BETA Meeting - Geneva, 1-2 March 2007

  8. Dependency Analysis • 20 Subsystems • 1 without declared dependencies (independent) • i.e. gLite • Can be potentially built at any time • 8 without dependants (non-critical) • i.e. POpt, MM, PDesign, Personalisation, Appl Layer, Annotation, Feature-extraction, Content-security • Have deps but no comp relies on them (can be post-poned if unavail.) • 11 with dependants (critical) • 5 from CL (DVOS, VDL, DIS, Keeper, BMM) • Process Resources • Process Execution • Content Management • 3 from I&SM (Search, Index, DIR) • Need to be built in the above order Release BETA Meeting - Geneva, 1-2 March 2007

  9. Dependency Analysis Collective Layer (VDL + DIS + DVOS + Keeper + BMM) gLite Feat Ext Proc Res CM Cont Sec Annot Proc Opt Proc Exec MM Proc Design Search + Index + DIR Personalisation Application Layer Release BETA Meeting - Geneva, 1-2 March 2007

  10. Integration ConfigurationsA Proposal Release BETA Meeting - Geneva, 1-2 March 2007

  11. Expected Time for Build Executions • Build execution times: • Whole DILIGENT project: approximately 4 hours • Individual subsystems: 10 mins to 1 hour • Most time spent in checkout (Build Server: CPU 2 x Xeon 2.8GHz, 1GB ram) • Build errors require: • Action from developers: bug fixing and possibly local build • Experience with Alpha (and Alex) tells: • Average fixing time for build bugs (e.g. bad commands and/or dependencies in ETICS, missing libraries and classes, etc.) in a build execution was half day • Difficult bugs (e.g. vcsPrefix mis-usage) took nearly two weeks to solve Release BETA Meeting - Geneva, 1-2 March 2007

  12. Release Candidate BetaExptected Times for Build Cycles Release BETA Meeting - Geneva, 1-2 March 2007

  13. Considerations • Consistent risk of missing a complete RC Beta for 31/4 • Some components scheduled for • 15 April (4 comps: VDL & CMS) • 31 April (3 comps: CMS & PES) • 31 May (1 comp: Search) • Unlikely to have 100% successful “build+deployTest” in one week for each integration build • Risk that some developments won’t complete by 31/3 even if scheduled • April TCOM • Possible solutions • Postpone deadline for a complete RC Beta • Remove components from Beta release Release BETA Meeting - Geneva, 1-2 March 2007

  14. Release BetaExptected Times for Build Cycles • Release Beta process is from 1/5 to 30/6 (2 months) • How long to fix bugs discovered in testing and produce a new integration build? Depends on: • Number and Severity of bugs (more difficult than build errors ) • Reactivity of developers (good, so far ) • Development still on-going (most likely to happen ) • Outcome of deployment testing (not expected to degrade ) • Not less than 10 days = No more than 6 build/test cycles • But we must also consider time for testing • Possible solution • Start testing earlier than 1/5 on available components Release BETA Meeting - Geneva, 1-2 March 2007

  15. ETICS Usage & Infrastructure Needs • Foreseen usage of ETICS: • Dynamic/Static dependencies • “Module renaming” issue not yet solved in current version. We’ll keep using static dependencies • Dependency scoping adoption (build/runtime) • Saves time when building and testing • Infrastructure Needs: • No further infrastructure requirements Release BETA Meeting - Geneva, 1-2 March 2007

  16. Build Scheduling and Execution • Alpha • All 0_1_X integration builds have been stopped • HEAD • Project and Subsystem builds are scheduled nightly • Beta • Subsystem integration builds will be scheduled for build as soon as available • Project integration builds will be triggered manually Release BETA Meeting - Geneva, 1-2 March 2007

  17. Configuration Naming • Alpha Release • Project-level configurations renamed to • org_diligentproject_0_1_1 • ... • org_diligentproject_0_1_4 • Beta Release • Module configurations will be • <<module_name>>_0_2_X • Project-level configurations will be • org_diligentproject_0_2_1 • org_diligentproject_0_2_2 • ... Release BETA Meeting - Geneva, 1-2 March 2007

More Related