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
Copy file name to clipboardExpand all lines: JenkinsJobs/Releng/FOLDER.groovy
+7-10Lines changed: 7 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -149,19 +149,16 @@ GitHub issue to track tagging the release, for example:
149
149
pipelineJob('Releng/makeVisible'){
150
150
displayName('Make Visible')
151
151
description('''\
152
-
The first part of doing a promotion -- the Rename And Promote job -- creates some scripts that make this deferred "make visible" part possible.
153
-
Therefore, they have to share a 'workspace', and the output of the first job must remain in place until its time to "make visible".
152
+
Make a 'release build', which was previously declared by running the 'Rename And Promote' job, visible.
153
+
The first part of a promotion -- the 'Rename And Promote' job -- puts the build at its final location, but keeps it hidden.
154
+
Therefore, both jobs have to share a 'workspace', and the output of the first job must remain in place until its time to "make visible".
154
155
''')
155
156
parameters {
156
-
stringParam('DROP_ID', null, '''\
157
-
The name (or, build id) of the build to rename and promote. Typically would be a value such as I20160530-2000 or M20160912-1000.
158
-
It must match the name of the build on the build machine.
157
+
stringParam('releaseBuildID', null, '''\
158
+
The id of the 'milestone', 'release-candidate' or 'GA-release' build to make visible.
159
+
Typically would be a value such as 'S-4.26M1-202209281800' or 'R-4.36-202505281830'.
160
+
It must match the name of the build on the download server.
159
161
''')
160
-
stringParam('CHECKPOINT', null, 'M1, M3, RC1, RC2, RC3 etc (blank for final releases).')
161
-
stringParam('SIGNOFF_BUG', null, 'The issue that was used to "signoff" the checkpoint. If there are no unit test failures, this can be left blank. Otherwise a link is added to test page explaining that "failing unit tests have been investigated".')
162
-
stringParam('TRAIN_NAME', null, 'The name of the release stream, typically yyyy-mm. For example: 2022-09')
163
-
stringParam('STREAM', null, 'Needs to be all three files of primary version for the release, such as 4.7.1 or 4.8.0.')
164
-
stringParam('DL_TYPE', null, "This is the build type we are promoting TO. I-builds promote to 'S' until 'R'.")
Copy file name to clipboardExpand all lines: RELEASE.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,9 +54,8 @@
54
54
4. Update the Location property to the "Specific repository for building against" in the mailtemplate.txt from promotion.
55
55
5. Commit Simrel updates to Gerrit
56
56
- Message should use year-month format, i.e "Simrel updates for Eclipse and Equinox for 2022-06 M1"
57
-
* Make the build visible
58
-
- Run the [Make Visible](https://ci.eclipse.org/releng/job/Releng/job/makeVisible/) job in Releng jenkins to make the promoted build visible on the download page.
59
-
- Parameters should match `Rename and Promote` job
57
+
* Run the [Make Visible](https://ci.eclipse.org/releng/job/Releng/job/makeVisible/) job in Releng jenkins to make the promoted build visible on the download page.
58
+
-`releaseBuildID`: the full id of the milestone, release-candidate or release build to make visible, e.g. `S-4.26M1-202209281800` or `R-4.36-202505281830`
60
59
* Send email that the M1 build is available
61
60
- Use the mail template from the promotion build [artifacts](https://ci.eclipse.org/releng/job/Releng/job/renameAndPromote/lastSuccessfulBuild/artifact/) in Jenkins to get the download urls.
62
61
- Make sure to mention that the Master branch is now again open for development.
0 commit comments