Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Platform-releng/Obsolete/Platform-releng-basics"
m (→Common build failures) |
m |
||
| Line 41: | Line 41: | ||
| − | ==Common build failures== | + | == Common build failures == |
| − | + | *Fail to fetch bundles from Orbit - symptom - java net url timeout in build failure message. Start a new build -> www.eclipse.org timeouts are intermittent. | |
| − | + | *"Error occurred while transforming repository" usually means that the bundle couldn't be fetched from Orbit. For example | |
| − | <pre> | + | <pre>Build M20090825-1330 (Timestamp: 200908251330): The following error occurred while executing this line: |
| − | Build M20090825-1330 (Timestamp: 200908251330): The following error occurred while executing this line: | + | |
/builds/M200908251330/org.eclipse.releng.eclipsebuilder/buildAll.xml:166: The following error occurred while executing this line: | /builds/M200908251330/org.eclipse.releng.eclipsebuilder/buildAll.xml:166: The following error occurred while executing this line: | ||
/builds/M200908251330/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.5.1.R35x_20090721/scripts/build.xml:78: The following error occurred while executing this line: | /builds/M200908251330/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.5.1.R35x_20090721/scripts/build.xml:78: The following error occurred while executing this line: | ||
| Line 60: | Line 59: | ||
/builds/M200908251330/src/fetch_org.eclipse.equinox.p2.user.ui.xml:10: The following error occurred while executing this line: | /builds/M200908251330/src/fetch_org.eclipse.equinox.p2.user.ui.xml:10: The following error occurred while executing this line: | ||
/builds/M200908251330/src/fetch_org.eclipse.equinox.p2.user.ui.xml:304: Error occurred while transforming repository. | /builds/M200908251330/src/fetch_org.eclipse.equinox.p2.user.ui.xml:304: Error occurred while transforming repository. | ||
| − | </pre> | + | </pre> |
| − | Since our build runs in an IBM lab, the http gets for orbit bundles from eclipse.org are usually redirected from download.eclipse.org to fullmoon.ottawa.ibm.com by the foundation. | + | Since our build runs in an IBM lab, the http gets for orbit bundles from eclipse.org are usually redirected from download.eclipse.org to fullmoon.ottawa.ibm.com by the foundation. This redirection can be avoided by changing the url in the orbit.map from download.eclipse.org to www.eclipse.org/external. Sometimes it will take a day or so for the internal mirror to get the latest orbit build, which can lead to build failures. |
| − | + | ||
| − | + | *Version of bundle in cvs doesn't match the one in the map files. Ask team to resubmit and start a new build. | |
| − | + | *SDKs fail to provision due to missing dependancies. There are releng logs on each test results page of the build that provide logs of the from the call to the p2 director to provision the zips. The Equinox team is helpful in finding the cause of the problem. See this page for an example. http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/buildlogs.php | |
| + | *The windows tests machines crash every so often. The event logs don't indicate that anything is wrong with the build. They are on the KVM next to the Eclipse rack in lab, on number 5 and 6. They can just be rebooted and logged into as the build user. I usually reboot these machines once a week so this doesn't happen. | ||
Revision as of 14:34, 25 August 2009
Basic overview of platform builds
Integration builds are in crontab of build user on build machine
Integration builds run from the tags of org.eclipse.releng
0 8 * * 2 cd /builds; /home/users/releng/buildTools/eclipse36/runIBuild-skipPerf
Nightly builds run from HEAD of org.eclipse.releng
0 20 * * 1,2,3,5,0 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf 0 20 * * 4,6 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf
3.5.x maintenance builds run from R3_5_maintenance branch of org.eclipse.releng
0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse35x/runMBuild
The machines used in the builds are listed in the FAQ.
The windows tests machines crash every so often. They can just be rebooted and logged into as the build user. The event logs don't indicate that anything is wrong with the build.
A script runs once a week to clean the test machines
0 18 * * 0 /home/users/releng/buildTools/scripts/buildblaster.sh
Older builds
3.4.2 test builds run from tags in 3.4.x maintenance branch
cd /builds; /home/users/releng/buildTools/eclipse34x/runKimTestMBuild
3.2.x test builds
cd /builds; /home/users/releng/buildTools/eclipse32x/runMTestBuild-skipPerf
Common build failures
- Fail to fetch bundles from Orbit - symptom - java net url timeout in build failure message. Start a new build -> www.eclipse.org timeouts are intermittent.
- "Error occurred while transforming repository" usually means that the bundle couldn't be fetched from Orbit. For example
Build M20090825-1330 (Timestamp: 200908251330): The following error occurred while executing this line: /builds/M200908251330/org.eclipse.releng.eclipsebuilder/buildAll.xml:166: The following error occurred while executing this line: /builds/M200908251330/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.5.1.R35x_20090721/scripts/build.xml:78: The following error occurred while executing this line: /builds/M200908251330/org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/master/customTargets.xml:18: The following error occurred while executing this line: /builds/M200908251330/org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/master/allElements.xml:16: The following error occurred while executing this line: /builds/M200908251330/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.5.1.R35x_20090721/scripts/genericTargets.xml:59: The following error occurred while executing this line: /builds/M200908251330/src/fetch_master.xml:11: The following error occurred while executing this line: /builds/M200908251330/src/fetch_master.xml:73: The following error occurred while executing this line: /builds/M200908251330/src/fetch_org.eclipse.sdk.xml:11: The following error occurred while executing this line: /builds/M200908251330/src/fetch_org.eclipse.sdk.xml:41: The following error occurred while executing this line: /builds/M200908251330/src/fetch_org.eclipse.platform.xml:11: The following error occurred while executing this line: /builds/M200908251330/src/fetch_org.eclipse.platform.xml:904: The following error occurred while executing this line: /builds/M200908251330/src/fetch_org.eclipse.equinox.p2.user.ui.xml:10: The following error occurred while executing this line: /builds/M200908251330/src/fetch_org.eclipse.equinox.p2.user.ui.xml:304: Error occurred while transforming repository.
Since our build runs in an IBM lab, the http gets for orbit bundles from eclipse.org are usually redirected from download.eclipse.org to fullmoon.ottawa.ibm.com by the foundation. This redirection can be avoided by changing the url in the orbit.map from download.eclipse.org to www.eclipse.org/external. Sometimes it will take a day or so for the internal mirror to get the latest orbit build, which can lead to build failures.
- Version of bundle in cvs doesn't match the one in the map files. Ask team to resubmit and start a new build.
- SDKs fail to provision due to missing dependancies. There are releng logs on each test results page of the build that provide logs of the from the call to the p2 director to provision the zips. The Equinox team is helpful in finding the cause of the problem. See this page for an example. http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/buildlogs.php
- The windows tests machines crash every so often. The event logs don't indicate that anything is wrong with the build. They are on the KVM next to the Eclipse rack in lab, on number 5 and 6. They can just be rebooted and logged into as the build user. I usually reboot these machines once a week so this doesn't happen.