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 "Releng-Tasks"
(→Run JUnits test with newer Java version:) |
|||
| Line 31: | Line 31: | ||
[https://ci.eclipse.org/releng/view/Builds/job/eclipse.releng.markUnstable/ Mark any IBuild as unstable when "Unanticipated comparator errors" occurs, you need to pass below Job args: <br> - Eclipse IBuild ID <br>- Bugzilla bug ID] <br> | [https://ci.eclipse.org/releng/view/Builds/job/eclipse.releng.markUnstable/ Mark any IBuild as unstable when "Unanticipated comparator errors" occurs, you need to pass below Job args: <br> - Eclipse IBuild ID <br>- Bugzilla bug ID] <br> | ||
| − | + | == Email Notification list: == | |
| − | + | ||
[https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/production/sdk/promotion/syncUpdateUtils.shsource#n385 P-build] <br> | [https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/production/sdk/promotion/syncUpdateUtils.shsource#n385 P-build] <br> | ||
| Line 38: | Line 37: | ||
Note: The lists are comma separated. You can add/remove individual mail-ids here. | Note: The lists are comma separated. You can add/remove individual mail-ids here. | ||
| − | + | == Run JUnits test with newer Java version: == | |
| − | + | ||
So, we need below things to be done e.g. let's consider Java12: <br> | So, we need below things to be done e.g. let's consider Java12: <br> | ||
| Line 47: | Line 45: | ||
3. We need to have the new Jenkins Jobs for IBuild and YBuild configuration created. So we cloned any of the existing Job e.g. Java11 and updated the JDK path in the script configuration. | 3. We need to have the new Jenkins Jobs for IBuild and YBuild configuration created. So we cloned any of the existing Job e.g. Java11 and updated the JDK path in the script configuration. | ||
| + | |||
| + | == Create new Y Builds == | ||
| + | |||
| + | Every time there's a new version of Java Language, the JDT and PDE teams work on adding the tooling support to Eclipse. This usually happens in a beta branch until it is time to merge the changes in master stream. For testing purposes as well as enabling dependent projects to use Gerrit, we need to create builds from the beta work. Here's the basic steps that need to be carried out: <br> | ||
| + | 1. Start with branching for project that contribute to the new language version. <br> | ||
| + | |||
| + | 2. Make the release changes as documented in [https://bugs.eclipse.org/548663 Bug 548663]: [13] Start creating Y builds from BETA_JAVA13 <br> | ||
| + | The commits has the details, but the three important changes are: <br> | ||
| + | - creating a new index page for the Y builds <br> | ||
| + | - listing the beta branches for the contributing repositories. <br> | ||
| + | - Update the mb4Y_hudson.sh with the appropriate branch information. (Make sure this is the script file used in the following Y build configuration in the shell command section. <br> | ||
| + | |||
| + | 3. Configure the Y build job [https://hudson.eclipse.org/releng/view/Builds/job/Y-build/configure] <br> | ||
| + | - Usually, nothing much needs to change, except the names of the branches, version etc. <br> | ||
| + | - As of now, maven has issues with > 8 JDK. Hence, make sure the job is configured with jdk 8 <br> | ||
| + | - Schedule if required <br> | ||
Revision as of 05:26, 6 December 2019
Page contains instructions for carrying out regular Eclipse Release engineering tasks. If you still have a query, please post the query in Releng Faq.
Contents
Routine releng tasks
Build failures
https://wiki.eclipse.org/Platform-releng-faq
Monitoring of JIPP jobs
Test Jobs
Linux GTK2 running on CentOS
Linux GTK3 running on CentOS
Linux GTK3 running on CentOS Java9
Mac OS X
Windows
Deployment jobs to repo.eclipse.org. If these fail gerrit jobs will fail
Deploys eclipse parent pom for use in gerrit
Deploys prereqs
Deploys JDT compiler
Cleanup and monitoring jobs
Verifies whether derby data base is working used in testing
Removed old builds based on the retention policy and updates download page
Verifies the I-build, M-build composites
Cleans up equinox builds
Mark any IBuild as unstable when "Unanticipated comparator errors" occurs, you need to pass below Job args:
- Eclipse IBuild ID
- Bugzilla bug ID
Email Notification list:
P-build
Y-build
Note: The lists are comma separated. You can add/remove individual mail-ids here.
Run JUnits test with newer Java version:
So, we need below things to be done e.g. let's consider Java12:
1. We need to installation of java12 on the test build machine, see bug: 544037
2. We need to have new releng configuration changes[Note we don't publish the newer Java version JUnits until officially supported by Eclipse], see bug: 543770
3. We need to have the new Jenkins Jobs for IBuild and YBuild configuration created. So we cloned any of the existing Job e.g. Java11 and updated the JDK path in the script configuration.
Create new Y Builds
Every time there's a new version of Java Language, the JDT and PDE teams work on adding the tooling support to Eclipse. This usually happens in a beta branch until it is time to merge the changes in master stream. For testing purposes as well as enabling dependent projects to use Gerrit, we need to create builds from the beta work. Here's the basic steps that need to be carried out:
1. Start with branching for project that contribute to the new language version.
2. Make the release changes as documented in Bug 548663: [13] Start creating Y builds from BETA_JAVA13
The commits has the details, but the three important changes are:
- creating a new index page for the Y builds
- listing the beta branches for the contributing repositories.
- Update the mb4Y_hudson.sh with the appropriate branch information. (Make sure this is the script file used in the following Y build configuration in the shell command section.
3. Configure the Y build job [1]
- Usually, nothing much needs to change, except the names of the branches, version etc.
- As of now, maven has issues with > 8 JDK. Hence, make sure the job is configured with jdk 8
- Schedule if required