| [wtp-releng] CBI build planning - meeting notes |
Folks,
Here are the notes that I took during the CBI build planning meeting. Others can feel free to post additional information or things covered. (There were times when I was listening and did not write much.) At the end are links to the bugs I opened as a result of our discussion.
Attendees:
Carl Anderson (WTP releng lead)
Thanh Ha (WTP releng committer)
Julio Chavez Ortiz (WTP releng committer)
Tran Le (WTP releng committer)
David Williams (WTP releng committer)
Roberto Sanchez
Ian Trimble
Chuck Bridgham
Carl - desired CBI build output:
A copy has to happen - this is a post build step - the product is left in product folders w/ funny name - during the copy, SNAPSHOT needs to be renamed to build ID
Can we use the current build output as the "committers" output? (Discussion ended with "No, it needs additional tweaking")
We could use a committer id to copy from the Hudson machine to the download area
If something goes wrong, we don't want to copy any of that output into the repository (to avoid comparator problems)
Dependencies - Thanh put variables into the parent pom file to determine the dependencies. We would need to parse them out.
David - the platform uses target files to specify exact dependencies.
Thanh - the Tycho build generates zip files already (Carl will check to see that it installs directly by unzipping)
Carl - can we set up the CBI build to still complete, even with JUnit problems
Thanh - currently, the build completes, but JUnits are turned off. With CBI, as soon as it builds, it runs a test. That's why the build fails if a JUnit fails- it runs the JUnits as soon as they are built.
David - there is a RedHat extension to Maven to allow all of the tests to run outside of (after) the build
David listed some possible issues to investigate:
Run a Tycho extra bundle- pomupdater - updates the pom with the appropriate version from the MANIFEST, prints out a reminder
There's a tool that uses a comparator and uses previous version if no changes- Carl and Thanh will work to set that up
Parse through the output (with /X) and see if the problems are worth stopping the build promotion
Post-build: Remove any assembly features
Tycho build does not create the MD5 checksum for the repository - processArtifacts (p2 ant task) can be run to create it.
Issues with nested jars - check to make sure that we don't have any (due to Java 7 pack issues)
Cautionary note: the BREEs are not always respected.
Carl - about Mickael's note- we can set up small builds, but we want all of WTP to build at the same time. We can have separate builds for smaller projects, but we want to have one build with consistent dependencies. We currently have a build just for JSDT that runs separate, and can have builds like that, but the output of that is not used in the overall WTP build.
David - WTP could set up a bunch of small builds that run in serial. That would still work.
Bugs opened as a result of this discussion:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425145
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425146
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425147
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425148
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425149
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425151
FWIW,
- Carl Anderson
WTP Build guy