Difference between revisions of "Platform UI/Build Submission"

From Eclipsepedia

Jump to: navigation, search
(How to do an Integration Build submission)
(How to do an Integration Build submission)
Line 13: Line 13:
 
### platform-ui
 
### platform-ui
 
### platform-ui-tests
 
### platform-ui-tests
### Note: the project org.eclipse.ui.carbon will have errors if you are not on carbon. You should have no other errors though.
+
### 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
 
## Load the project org.eclipse.releng
 
# Run the test suites.  To do this:
 
# Run the test suites.  To do this:
Line 25: Line 25:
 
# Leave selected "Use the default map project (org.eclipse.releng)". Click Next>.
 
# 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>.
 
# 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 awhile while cvs info is checked.
+
# The next step takes some time while cvs info is checked.
# Select all text and paste into your mailer.  Later, use this text to send an email to platform-ui-dev@eclipse.org notifying of build submission.
+
# The next page will be "Changed Projects".  Check the "Generate Build Notes" option at the bottom. Click Next>
# On the resulting page, check the "Generate Build Notes" option at the bottom of the dialog.  Click Next>.
+
# The system will be busy for a minute or two.
# Select "Update the Build Notes File" checkbox at the top, and fill in the build notes file field as "/org.eclipse.ui/buildnotes_workbench.html"  
+
# 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.
# Type in the build tag, which is I or M (for integration or maintenance) followed by the build date-time. Next>.
+
# 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"  
# Enter the commit comment for the changed configuration file.  Type "Submission for X-Y" where X-Y is the build date-time.
+
# 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 type in as you'll need it next. Leave the other options as is. 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.

Revision as of 22:50, 26 November 2007

How to do an Integration Build submission

Prep:

  1. It is best to keep an install/workspace around solely for the purpose of build submission. Take the latest milestone.
  2. Install releng tools into your eclipse install
    1. go to http://download.eclipse.org/eclipse/downloads/
    2. pick the build matching your install
    3. scroll to bottom, last section should be titled org.eclipse.releng.tools plug-in
    4. download to your install dir. Note: to verify its installed, start up eclipse, pick a project and popup menu. You should see "Fix Copyrights..."

Steps:

  1. Load contents from CVS
    1. Check Out the two modules(they will be at the bottom)
      1. platform-ui
      2. platform-ui-tests
      3. 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.
    2. Load the project org.eclipse.releng
  2. Run the test suites. To do this:
    1. "Close Project" org.eclipse.ui.carbon if you are not on Carbon. Verify you now have no compile errors.
    2. Open up Run->Run Configurations
    3. 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.
    4. 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.
    5. "Open Project" org.eclipse.ui.carbon if you closed it above.
    6. The act of running the tests will modify some of the test suite projects. Reload them to clear the local changes.
  3. Select all the projects, pop up the menu and pick Team->Release...
  4. Leave selected "Use the default map project (org.eclipse.releng)". Click Next>.
  5. 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>.
  6. The next step takes some time while cvs info is checked.
  7. The next page will be "Changed Projects". Check the "Generate Build Notes" option at the bottom. Click Next>
  8. The system will be busy for a minute or two.
  9. 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.
  10. 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"
  11. 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 type in as you'll need it next. Leave the other options as is. Next>.
  12. 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.