[RelEng] Update build configuration in release preparation pipeline

and simplify the definition and activation of the RC schedule:
Update the cron-trigger to it's final value immediately. The extra
builds are then triggered when the RC period arrives without activating
that schedule manually.

Author: HannesWell

JenkinsJobs/Builds/FOLDER.groovy

@@ -8,24 +8,20 @@ for (STREAM in config.Streams){
 	def BRANCH = config.Branches[STREAM]
 
 	pipelineJob('Builds/I-build-' + STREAM){
+		//TODO: disable job initially if it doesn't exist before?
 		description('Daily Eclipse Integration builds.')
 		properties {
 			pipelineTriggers {
 				triggers {
 					cron {
 						spec('''TZ=America/Toronto
-# format: Minute Hour Day Month Day of the week (0-7)
-
+# format: Minute Hour Day Month Day-of-week (1-7)
 # - - - Integration Eclipse SDK builds - - - 
-# 2025-09 Release Schedule
-# Normal : 6 PM every day (11/6 - 27/8)
+# Normal Schedule: 6 PM every day
 0 18 * * *
 
-
-# RC Schedule 
-# Post M3, no nightlies, I-builds only. (Be sure to "turn off" for tests and sign off days)
-0 6 15-27 8 5-7,1-3
-0 18 15-27 8 5-7,1-3
+# RC Schedule: Additional build at 6 AM every day
+0 6 15-29 8 *
 ''')
 					}
 				}

JenkinsJobs/Releng/prepareNextDevCycle.jenkinsfile

@@ -44,9 +44,9 @@ pipeline {
 					// E.g. next to: https://github.com/eclipse-simrel/.github/blob/main/wiki/SimRel/2025-09.md
 					def m1Date = parseDate(readParameter('M1_DATE'))
 					def m2Date = parseDate(readParameter('M2_DATE'))
-					def m3Date = parseDate(readParameter('M3_DATE'))
+					m3Date = parseDate(readParameter('M3_DATE'))
 					def rc1Date = parseDate(readParameter('RC1_DATE'))
-					def rc2Date = parseDate(readParameter('RC2_DATE'))
+					rc2Date = parseDate(readParameter('RC2_DATE'))
 					def gaDate = parseDate(readParameter('GA_DATE'))
 					if (!(m1Date < m2Date && m2Date < m3Date && m3Date < rc1Date && rc1Date < rc2Date && rc2Date < gaDate)) {
 						error "Dates are not in strictly ascending order: ${M1_DATE}, ${M2_DATE}, ${M3_DATE}, ${RC1_DATE}, ${RC2_DATE}, ${GA_DATE}"
@@ -120,6 +120,28 @@ pipeline {
 				replaceInFile('production/testScripts/configuration/streamSpecific.properties', [
 					"for ${PREVIOUS_RELEASE_VERSION}.0 builds" : "for ${NEXT_RELEASE_VERSION}.0 builds",
 				])
+				replaceInFile('JenkinsJobs/JobDSL.json', [
+					/"${PREVIOUS_RELEASE_VERSION}"/ : /"${NEXT_RELEASE_VERSION}"/,
+				])
+				script {
+					def rcSchedule = null
+					if (m3Date.monthValue == rc2Date.monthValue) { // RC period is completely within one month
+						rcSchedule = "0 6 ${m3Date.dayOfMonth}-${rc2Date.dayOfMonth} ${m3Date.monthValue} *"
+					} else if ((m3Date.monthValue + 1) == rc2Date.monthValue) { // RC period reaches beyond a month boundary
+						rcSchedule = """\
+						0 6 ${m3Date.dayOfMonth}-31 ${m3Date.monthValue} *
+						0 6 1-${rc2Date.dayOfMonth} ${rc2Date.monthValue} *
+						""".stripIndent().trim()
+					} else {
+						error "M3 and RC2 are more than one month apart: m3-month=${m3Date.monthValue}, rc-month=${rc2Date.monthValue}"
+					}
+					echo "RC schedule:\n${rcSchedule}"
+					replaceAllInFile('JenkinsJobs/Builds/FOLDER.groovy', [
+						// The previous RC periode may extend beyond a month boundary, too
+						'0 6 [\\d-]+ \\d+ \\*(\\R0 6 [\\d-]+ \\d+ \\*)?' : rcSchedule,
+					])
+					//TODO: add Y-build folder !
+				}
 
 				commitAllChangesExcludingSubmodules("Update versions to ${NEXT_RELEASE_VERSION} in build scripts")
 			}
@@ -331,6 +353,10 @@ pipeline {
 
 @groovy.transform.Field
 def githubAPI = null
+@groovy.transform.Field
+def m3Date = null
+@groovy.transform.Field
+def rc2Date = null
 
 // --- utility methods
 

JenkinsJobs/YBuilds/FOLDER.groovy

@@ -9,21 +9,18 @@ for (STREAM in config.Streams){
 	def BRANCH = config.Branches[STREAM]
 
 	pipelineJob('YPBuilds/Y-build-' + STREAM){
+		//TODO: disable job initially if it doesn't exist before?
 		description('Daily Maintenance Builds.')
 		properties {
 			pipelineTriggers {
 				triggers {
 					cron {
 						spec('''TZ=America/Toronto
-# format: Minute Hour Day Month Day of the week (0-7)
-
-#Daily Y-build
-0 10 * * *
-#milestone week
-#0 6 * * 2
-#0 6 * * 4
-#
-#0 2 21 7 4
+# format: Minute Hour Day Month Day-of-week (1-7)
+# Normal Schedule: 10 AM every second day
+0 10 * * 2,4,6
+# RC Schedule: 10 AM every day
+0 10 15-29 8 *
 ''')
 					}
 				}

RELEASE.md

@@ -5,7 +5,6 @@
 ## Milestone and RC Releases
 
 ### Friday before release week:
- * Update [I-builds job definition](JenkinsJobs/Builds/FOLDER.groovy) to build on the milestone schedule (Twice daily at 06:00 EST and 18:00 EST except Thursday).
  * Create or update prerequisite issues for tracking ECF, EMF and Orbit
  * Send reminder email for upcoming RC week to [email protected], [email protected], [email protected] and [email protected]
    * [Example from 4.30 RC1](https://www.eclipse.org/lists/platform-dev/msg03924.html) but the usual schedule:
@@ -49,9 +48,7 @@
            4. Update the Location property to the "Specific repository for building against" in the mailtemplate.txt from promotion.
            5. Commit Simrel updates to Gerrit
               - Message should use year-month format, i.e "Simrel updates for Eclipse and Equinox for 2022-06 M1"
-       * For **Milestone builds** return the I-builds to the normal schedule.
      * **After RC1**
-       * Leave the I-builds running on the milestone schedule for RC2. 
        * Comment on EMF, ECF and Orbit issues to ask for final release builds.
      * **After RC2**
        * (optional) Disable the automatic [nightly cleanup](https://ci.eclipse.org/releng/job/Cleanup/job/dailyCleanOldBuilds/) of I-builds