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: README.adoc
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -345,6 +345,7 @@ The security release follows the same process as the stable one except that arti
345
345
.. `JENKINS_VERSION` set to the final release version that will be packaged. If set to 'stable' or 'weekly' then the packaging job will try to guess the version based on what was pushed to the maven repository. cfr settings.
346
346
.. `PACKAGING_GIT_BRANCH` set to the appropriated jenkinsci/packaging branch
347
347
.. `MAVEN_REPOSITORY_NAME` set to the maven repository name where we are going to publish staging maven artifacts. This is also the source location used by the packaging job to build distribution packages
348
+
<<<<<<< HEAD
348
349
. Trigger the generic Release link:https://release.ci.jenkins.io/job/core/job/release/[job] from the appropriated branch like `security-stable-2.235`
349
350
.. Force repository scan
350
351
.. Trigger the first build to have access to job parameter and immediately abort it
@@ -362,6 +363,10 @@ The security release follows the same process as the stable one except that arti
362
363
... `MAVEN_STAGING_REPOSITORY_PROMOTION_ENABLED` set to true
363
364
... `GIT_STAGING_REPOSITORY_PROMOTION_ENABLED` set to false as we prefer to do it manually once everything is done
364
365
... `VALIDATION_ENABLED` set to true
366
+
=======
367
+
.. `RELEASELINE` set the releaseline '-stable' for stable releases and nothing for weekly
368
+
. Trigger the security link:https://release.ci.jenkins.io/blue/organizations/jenkins/core%2Fsecurity%2Frelease/branches/[job]
0 commit comments