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.
Releng-Tasks
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.