Platform UI/Build Submission
How to do an Integration Build submission
The following describes how to do an integration build submission. The steps for doing a maintenance submission are mostly the same except for how you set up the workspace in the first place. Perhaps someone could detail that.
Prep
- It is best to keep an install/workspace around solely for the purpose of build submission. Take the latest milestone.
- Install releng tools into your eclipse install
- P2 Steps
- Go to Help->Update
- Add the following site http://download.eclipse.org/eclipse/testUpdates
- The releng tools show up when you enter "releng" in the filter field
- Old Steps
- go to http://download.eclipse.org/eclipse/downloads/
- pick the build matching your install
- scroll to bottom, last section should be titled org.eclipse.releng.tools plug-in
- download to your "dropins" dir in your install dir. Note: to verify its installed, start up eclipse, pick a project and popup menu. You should see "Fix Copyrights..."
- P2 Steps
Steps
- Load contents from CVS
- Check Out the two modules(they will be at the bottom)
- platform-ui
- platform-ui-tests
- Note: the project org.eclipse.ui.carbon will have errors if you are not on carbon. At time of writing, it generated 53 errors. You should have no other errors though.
- Load the project org.eclipse.releng
- Check Out the two modules(they will be at the bottom)
- Run the test suites. To do this:
- "Close Project" org.eclipse.ui.carbon if you are not on Carbon. Verify you now have no compile errors.
- Open up Run->Run Configurations
- Under JUnit Plug-in Test, select each test in turn and run. You can't multi select, so each test is run on its own.
- Note: The JFace-All and RCP Test Suite require that the workbench have focus otherwise you will get false errors. Go get a coffee while running these since you can't use your machine.
- "Open Project" org.eclipse.ui.carbon if you closed it above.
- The act of running the tests will modify some of the test suite projects. Reload them to clear the local changes.
- Select all the projects, pop up the menu and pick Team->Release...
- Leave selected "Use the default map project (org.eclipse.releng)". Click Next>.
- There will be a tree with three top level items all checked. Deselect the first two, leaving "ui.map" and its children selected. Click Next>.
- The next step takes some time while cvs info is checked.
- The next page will be "Changed Projects". Check the "Generate Build Notes" option at the bottom. Click Next>
- The system will be busy for a minute or two.
- You will see the "Notes for Build Changes" page. Select all the text and paste into your mailer. Later, use this text to send an email to platform-ui-dev@eclipse.org notifying of build submission.
- Check the "Update the Build Notes File" checkbox at the top, and fill in the build notes file field as "/org.eclipse.ui/buildnotes_workbench.html". Click Next>.
- Type in the build tag, which is I or M (for integration or maintenance) followed by the build date-time (not the current date/time, the one at which the build will be run). So for example, I20071127-0800. Copy the text you typed in as you'll need it next. Leave the other options as is. Click Next>.
- Enter the commit comment for the changed configuration file. Type "Submission for X-Y" where X-Y is the build date-time you entered for the tagging and copied.