Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Linux Tools Project/Releng
< Linux Tools Project
Revision as of 10:30, 1 April 2009 by Unnamed Poltroon (Talk) (→Adding a new test plugin to those that are run during the automated build)
Contents
Linux Tools Release Engineering Procedures
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
- Add the test plugin(s)/feature(s) to your sub-project's PSF
- 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.