|
|
| (74 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | This document is the "plan", and more working notes for moving to CBI-based builds.
| + | #REDIRECT [[Category:Eclipse_Platform_Releng]] |
| − | | + | |
| − | =Main Criteria for moving to CBI based build for Kepler=
| + | |
| − | | + | |
| − | # Have same output deliverables as current build: zips, repository, etc. (For Equinox and Eclipse) | + | |
| − | # (Be able to reproduce exact same build, given a tag (or tags) to start the build with.)
| + | |
| − | # Same warnings (and compile errors, if any) as PDE based build.
| + | |
| − | # Be able to run our JUnit tests, with same results, as PDE based build.
| + | |
| − | # Run a binary comparator against the bundles to ensure that they are the same binary content as the regular bundles.
| + | |
| − | :[Not sure how to do this since "qualifier algorithm" is different].
| + | |
| − | # Qualifiers not change (except for branding bundles) if the content has not changed.
| + | |
| − | # All bundles signed.
| + | |
| − | # Final I-build type repository have same content and metata as PDE based build (nothing missing, nothing extra).
| + | |
| − | # Be easy to fit in to current workflow of automated builds and tests of "nightlies", I-builds, milestones (i.e. committers have to know
| + | |
| − | what to do to "release" something for a build, how to "freeze" changes at a certain point).
| + | |
