You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[RelEng] Consider next java release date for Y-build schedule
Explicitly specify a limited cron based schedule for Y-builds too that
is either aligned with the Eclipse release or a Java-release.
If no Java release happens soon after the Eclipse release the schedule
ends two days before RC2 (similar to I-builds).
If a Java release happens soon after the Eclipse release (and a JDT
patch is provided after the Eclipse release), the Y-build schedule is
extended until shortly after the java release date and the schedule and
the Y-build cadence is increased in the 'RC-phase'.
Copy file name to clipboardExpand all lines: JenkinsJobs/Releng/FOLDER.groovy
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,7 @@ Useful for debugging and to very that the pipeline behaves as intended.
88
88
stringParam('RC1_DATE', null, 'Release-Candidate 1 end date in the format yyyy-mm-dd, for example: 2025-08-22')
89
89
stringParam('RC2_DATE', null, 'Release-Candidate 2 end date in the format yyyy-mm-dd, for example: 2025-08-29')
90
90
stringParam('GA_DATE', null, 'Final general availability release date in the format yyyy-mm-dd, for example: 2025-09-10')
91
+
stringParam('NEXT_JAVA_RELEASE_DATE', null, 'Release date of the next nww Java version, if it is released shortly after the Eclipse release (i.e. shortly after the <em>GA_DATE</em> specified above, usually for odd release versions), else left blank (usually for even releases). Value is in the format yyyy-mm-dd, for example: 2025-09-16')
// Disable Y-build schedule only after the previous releases job is not updated (on the master) anymore, because Y-build jobs run beyond the Eclipse release if a new java release is imminent
0 commit comments