Skip to main content

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.

Jump to: navigation, search

Platform-releng-troubleshooting

Revision as of 16:59, 11 December 2008 by Kmoir.ca.ibm.com (Talk | contribs)

Basic build troubleshooting

The builds run from cron on our build machine as follows

integration builds 0 8 * * 2 cd /builds; /home/users/releng/buildTools/eclipse34/runIBuild

subsequuent integration build without perf tests is run like this if a rebuild is requested (cd /builds; /home/users/releng/buildTools/eclipse34/runIBuild-skipPerf)

nightly builds 10 0 * * 1,2,3,5,6 cd /builds; /home/users/releng/buildTools/eclipse34/runNBuild-skipPerf 10 0 * * 4,0 cd /builds; /home/users/releng/buildTools/eclipse34/runNBuild

maintenance builds 0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse33x/runMBuild

Basic build troubleshooting

Common Reasons for build failures

  1. Missing dependancies due to erroneous map file submission. Check that the map file refers to a version of a project that exists in the repo.
  2. Missing dependancies due to errors in Manifest or missing dependancies in manifest.

In the both cases, the error sent to the releng list will look something like this... http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg09778.html

Back to the top