Bugzilla – Full Text Bug Listing
| Summary: | [plan] build automatization, daily builds, integration builds | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Markus Knauer <mknauer> |
| Component: | Geclipse | Assignee: | Ariel Garcia <aog-ecl> |
| Status: | CLOSED FIXED | QA Contact: | Markus Knauer <mknauer> |
| Severity: | major | ||
| Priority: | P1 | CC: | mknauer |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
partially available in M3, but moving to M4 build process available and working... assigning bug to Ariel For completeness, I post the URL of the continous integration system here: http://iwr-geclipse.fzk.de:8443/luntbuild/app.do The autobuild system is functional, further improvements will be tracked in separate Bugs. Closing this one. Closing this one. |
Taken from the g-Eclipse Technical Annex: The build system will ensure quality of work of the distributed team by identifying problems as early as possible. * Daily build from the latest code checked in by all teams and the published results from the HEAD build and tests will provide immediate feedback to the developers. * Regular bi-weekly integration builds will force the teams - to explicitly release versions of their code to be included - the project members to produce a build that is good enough to use for further developments - the team to solve occurring bugs in the recovery build on the next day - the developers to fulfill the announced build schedules * Milestone Builds that are aimed to be production quality - milestone deliveries include a "new and noteworthy" document that guides users to new and improved functionality