Jump to: navigation, search

Europa Build Workshop Breakout Results

Revision as of 11:59, 13 September 2006 by Codeslave.ca.ibm.com (Talk | contribs)

Build Best Practices Breakout

(computer crashed in the middle of typing in the result)

  1. Proper version numbering
  2. Making builds reproducible
  3. Tag files from each release with the same human-readable tag
  4. Track API changes
  5. avoid circular dependencies
  6. documentation up-to-date; current link available on website; remove old contents
  7. backup redundant systems
  8. separate publishing script from “build” (compilation)
  9. able to turn functions on the build on or off e.g. turn off publishing
  10. regularly scheduled builds
    1. public humiliation
    2. send email to mailing list
    3. send email to plug-in owner
  11. have an update site; optimize update sites
  12. pack 200
  13. feature design – group plug-ins based on functional grouping

Buckminster/Maven

  • Common model
    • Backbone
    • Graphical model input
    • Buckminster and Buckminster model
    • Maven in Eclipse and Maven model
    • Maven
  • Suggest that they adopt a Europa project and help revise that project's build. Nick volunteered one of the smaller EMFT projects; another candidate is BIRT (Sue); don't want to take on too much - want one/few good success stories rather than broad swath of mediocrity
  • Document the process as a part of working with one of the projects.

RSS

  • One artifact of an EMF build (Thu 00:00 EDT) being promoted (Thu 01:00 EDT) is that an RSS file is updated and scp'd to download.eclipse.org
  • The UML project consumes the RSS feed to trigger a new build (Thu 03:00 EDT)
  • Platform will be publishing RSS soon (very soon)
  • UML assumes a linear ordering (reads just one feed, not many feeds, since it depends on EMF which in turn depends on Eclipse)
  • RSS feed supports a variety of status codes: build done, tests done, etc. though a definitive list has yet to be stated.
    • This is a TODO for Nick to define the spec, though I'm of course open to suggestions to make the spec useful to all
  • RSS is on a download site so that mirrors will be updated with files and then the RSS - as such, you can watch a given mirror's copy of the feed in order to know when the mirror's got new upstream project bits on which you depend
  • RSS is committed to CVS for history/auditing
  • Dennis and Nick recommend this should be adopted for cross-project notifications (and optionally response) by Europa projects to try it, use it and improve it
  • Nick is willing to be the point person for initial communication, documentation, assistance
  • Which builds to publish for? nightly? integration? good? failed?
    • Kim brings up "how to define what 'good' is - what if it was a test fixture failure (as determined by a human) instead of a test failure - then the human says 'this is a good build' and yet the RSS says 'bad'".
    • Bjorn argues for more information rather than less - let the downstream consumers decide what to do with the extra information (e.g., ignore nightly builds, ignore bad builds, ...)
    • As such, we would suggest that if you publish a build, it should includes an RSS entry (be it of type N or I/M or S or R). Build status in the feed (PASSED, FAILED, IN PROGRESS, PENDING, UNKNOWN, etc.) can default to a given state and be updated as needed by Ant tasks

Bjorn, Ward, Nick (and others) would like to see everyone adopting the process of publishing feeds within the next month, and listening to feeds (and determining how to respond) the month thereafter. Ideally, this means we could try some RSS build cascades (or at least RSS information cascades) by early November. There was a general consensus that this was a good idea, so I'm hoping everyone can commit to this schedule.

--nickb

Nick's Tools

Nick shows off new Search CVS tool for browsing CVS and Bugzilla. (This tool is also linked from our generated release notes.) If you'd like your project indexed in this database, add your name and /cvsroot/path/to/project(s) here. I'll update this when you're indexed so you can play with it.

  • org.eclipse.corona
  • org.eclipse.emf, org.eclipse.emf.releng.build, org.eclipse.emf.ecore.sdo, org.eclipse.xsd
  • org.eclipse.emft
  • org.eclipse.gmf
  • org.eclipse.uml2, org.eclipse.uml2.releng
  • www
    • emf
    • emft
    • uml2

Buckminster Demo

The Buckminster team gave a demo.

Common Build Infrastructure

Goals:

  • Shorter learning curve / wuicker startup
  • Consistency
  • Best practices
  • Outreach Activity

Scope:

  • What is provided / what form
  • Benefits to Foundation / Projects
  • Committers and projects need not worry about so much setup/infrastructure

Wishlist

  • vservers / vmware instances to start builds from clean states
  • add build infrastructure to vserver image file so more consistency between
  • common management interface / new committer tools on dev.eclipse?
  • decouple java compilation from native building from packaging
  • project dashboard interface, eg., http://packages.qa.debian.org/f/firefox.html
  • Experiment: set up a vserver for Buckminster/BIRT builds


Eclipse.org Current Build Infrasctructure Offerings

  • Option 1: unmanaged vserver (*.eclipse.org)
    • users get root access, running Xen
    • no management provided by Eclipse
    • two physical servers to share load
    • currently limited by IP address pool
    • hardware limited by budget
    • requires extra maintenance / security / duplication of effort
  • Option 2: managed "massive massive quad-CPU beast": build.eclipse.org
    • Backups provided, no root access

Best Practices

  • Let projects choose whether to publish builds from build server to mirrored