[RelEng] Split stream, branch and schedule configuration for I/Y builds #3351
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Split the configuration of built branches per stream and specify it individually per build type (I- and Y-build). Additionally specify individually per build type and stream the cron trigger schedule of the corresponding build. This allows to configure all managed builds individually. When preparing a new release, add new and move old stream as before. But preserve the old build's schedule and don't overwrite especially the Y-build schedule with the new streams schedule even if a Java release is imminent (this wrongly happened before). For Y builds, also add the new stream immediately, but disable it, when a java release is imminent and the the new BETA-Java branch is not created. The old stream's Y-build can then continue until the Java release to feed the P-build and the new build can be activated once ready.
Member
Author
|
The verification build doesn't test this, but my manual testing was successful, so I'm submitting this immediately. |
HannesWell
commented
Sep 22, 2025
Comment on lines
-58
to
+59
| * Update the Y-build (Y_build.groovy)[JenkinsJobs/YBuilds/Y_build.groovy]. | ||
| * Update the Y-build configuration in the (build.jenkinsfile)[JenkinsJobs/Builds/build.jenkinsfile] | ||
| - Update `branchLabel` and `typeName` to the name of the new java version | ||
| * Remove the disablement of the current stream in the Y-build configuration in the (JobDSL.json)[JenkinsJobs/JobDSL.json] (should be the only Y-build stream). | ||
| * Update and rename the java repository files in (cje-production/streams)[cje-production/streams] | ||
| - Repos without a BETA_JAVA## branch should be set to master | ||
| * Add unit tests for the new java version in (JenkinsJobs/YBuilds)[JenkinsJobs/YBuilds] | ||
| * Add Y builds to (Create Jobs)[https://ci.eclipse.org/releng/job/Create%20Jobs/] in Jenkins if they've been removed | ||
| - Repos without a `BETA_JAVA##` branch should be set to master | ||
| * Add unit tests for the new java version in (JenkinsJobs/YBuilds)[JenkinsJobs/YBuilds] and (build.jenkinsfile)[JenkinsJobs/Builds/build.jenkinsfile] |
Member
Author
There was a problem hiding this comment.
@MohananRahul, @subyssurendran666 please consider these changes when you prepare the Y-builds for Java-26 BETA.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split the configuration of built branches per stream and specify it individually per build type (I- and Y-build). Additionally specify individually per build type and stream the cron trigger schedule of the corresponding build.
This allows to configure all managed builds individually.
When preparing a new release, add new and move old stream as before. But preserve the old build's schedule and don't overwrite especially the Y-build schedule with the new streams schedule even if a Java release is imminent (this wrongly happened before).
For Y builds, also add the new stream immediately, but disable it, when a java release is imminent and the the new BETA-Java branch is not created. The old stream's Y-build can then continue until the Java release to feed the P-build and the new build can be activated once ready.
Follow-up on respectively complements