Presentation is loading. Please wait.

Presentation is loading. Please wait.

A DΙgital Library Infrastructure on Grid EΝabled Technology Release Beta Build and Deployment Testing.

Similar presentations


Presentation on theme: "A DΙgital Library Infrastructure on Grid EΝabled Technology Release Beta Build and Deployment Testing."— Presentation transcript:

1 A DΙgital Library Infrastructure on Grid EΝabled Technology Release Beta Build and Deployment Testing

2 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 2 Builds Name  Alpha  Naming convention: 0_1_X  HEAD  Naming convention: HEAD  Beta  Naming convention: 0_2_X  Always the same subsystem/components configurations until release candidate ?  at least at this stage we should lock the RC configuration !

3 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 3 Builds Execution  HEAD configurations:  Project builds scheduled nightly  BETA configurations:  Project builds scheduled nightly  Subsystem integration builds by request  method1: submit link in build report webpage  method2: ask Alex  Infrastructure  local build: grids16.eng.it  remote build: only possible if etics remote build can publish artifacts in a protected repository

4 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 4 Deployment Testing Execution  Libraries: automatic  Services: based on the deploy test tool  REQ: service undeployment in DL Management  REQ: get service ID from service name in PR  Portlets: deployment script needs to be provided  Infrastructure  local tests (remote test can also be tested)  independent infrastructure

5 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 5 Schedule  Expected execution times:  Build full project: ~4 hours  Build individual subsystems: ~1 hour  Deploy test project: ~6 hours (services only!)  However:  fixing bugs requires some time:  Even using Savane to set up the bugs publication  Even with normal developer support  time needed to run deployment test in portlets is unknown  Major progresses at least = 1 week

6 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 6  12/03: org_diligentproject_0_2_0  19/03: org_diligentproject_0_2_1 ...  16/04: org_diligentproject_0_2_5 (last comp. integrated)  23/04: org_diligentproject_0_2_6 (possible RCB) Schedule AlphaBeta Number of weeks to produce RC86 Number of components89151 Number of integrations configurations46

7 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 7 Repositories  Build Server (grids16.eng.it)  Stores all different BUILDs of all configurations  Should not be available to the public  Services, Libraries, Portlets and Service Archives  Repository (grids17.eng.it)  Stores the last BUILD  Used by the deployment testing  Services, Libraries, Portlets and Service Archives  Distribution Repository (grids16.eng.it)  Not integrated with DILIGENT Portal  Independent access control

8 Digital Libraries Powered by the Grid Release Beta Meeting - Geneva 8 Logistics  Clarify developers about:  how to declare their services available  change Savane status field to “Done”  create an ETIC configuration and associate it with the subsystem conf.  bug fixing strategy  bug fixing is done on HEAD, a new tag created, the conf. updated  the naming rules to be used  usage of ETICS client  (set up a TCom conf call to explain)  Have 1 weekly phone call (on Fridays)  summarize the progresses of the week (ALL)  present the components to be included in next week integration build (ENG)


Download ppt "A DΙgital Library Infrastructure on Grid EΝabled Technology Release Beta Build and Deployment Testing."

Similar presentations


Ads by Google