Revision as of 10:46, 1 April 2009

Linux Tools Release Engineering Procedures

Galileo or Ganymede?

Adding a new feature to the build

• add the feature to the org.eclipse.linuxtools.all feature.xml

Building locally

• check out releng/{trunk,branches/Galileo}/org.eclipse.linuxtools.releng
• right-click on build.xml and run it as an ant build

Adding a new test plugin to those that are run during the automated build

• Create test plugin(s) (ex. org.eclipse.linuxtools.mycoolfeature.ui.tests)
  • Add a test.xml like the other suites (this is used when the automated build is run)
  • Ensure test.xml and any resources are listed in build.properties
  • Check your plugin(s) into SVN
• If you are adding an entire test feature, add it to the included features in org.eclipse.linuxtools.test-feature
• If it's just a single test plugin (or more than one), add it/them to the included plugins in org.eclipse.linuxtools.test-feature
• Ensure the test plugin(s) do not get packed in the including feature.xml (ie. don't have "unpack=false" in the relevant plugin section of feature.xml)
• Add the test plugin(s) to the list of those to be run in testing.properties in org.eclipse.linuxtools.releng
• Add the test plugin(s)/feature(s) to the map file (be sure to update both the Galileo branch and trunk)
• Add the test plugin(s)/feature(s) to your sub-project's PSF (again, be sure to update both Galileo branch and trunk)
• Verify that your tests are built/run with a local build (see instructions on this page)

The next time a build happens, your test plugin(s) will be built and run. If you need a build pushed sooner than the next 6 hour mark when our scheduled builds happen, speak with Andrew Overholt.