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: .github/ISSUE_TEMPLATE/1-lts-release-checklist.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,14 +25,13 @@ This role should rotate between LTS releases
25
25
If the last release of the preceding LTS line is a security release, consider making the matching weekly release the [new LTS baseline](https://groups.google.com/g/jenkinsci-dev/c/ca7Lp0x6Kqs/m/QwHj66hZAgAJ).
26
26
For example, 2.462.3 LTS and 2.479 were security releases and it is simpler to use 2.479 as baseline than 2.477.
27
27
28
-
-[ ] Create or update release branch in [jenkinsci/jenkins](https://github.com/jenkinsci/jenkins), e.g. `stable-2.387`, use the [init-lts-line](https://github.com/jenkins-infra/release/blob/master/tools/init-lts-line) script or carry out the equivalent steps therein.
28
+
-[ ] Create or update the release branches in all the repositories below, e.g. `stable-2.387` with the [init-lts-line](https://github.com/jenkins-infra/release/blob/master/tools/init-lts-line) script or carry out the equivalent steps therein. For more info, refer to [stable](https://github.com/jenkins-infra/release#stable).
-[ ] Create or update release branch in [jenkins-infra/release](https://github.com/jenkins-infra/release), e.g. `stable-2.387`. Strike out for initial release.
31
-
-[ ] Modify the `RELEASE_GIT_BRANCH` and `JENKINS_VERSION` values in the environment file (`profile.d/stable`) to match the release.
32
-
-[ ] Modify the `PACKAGING_GIT_BRANCH` value in the packaging script (`Jenkinsfile.d/core/package`) to match the release.
33
-
- For more info, refer to [stable](https://github.com/jenkins-infra/release#stable).
34
-
35
-
-[ ] Create or update release branch in [jenkinsci/packaging](https://github.com/jenkinsci/packaging), e.g. `stable-2.387`. Strike out for new point release.
33
+
-[ ] Check with the Jenkins Infrastructure team for backports on both repositories [jenkinsci/packaging](https://github.com/jenkinsci/packaging) and [jenkins-infra/release](https://github.com/jenkins-infra/release) as per https://github.com/jenkins-infra/release/blob/master/docs/releases.md#open-a-backporting-pr.
34
+
- A message in the Matrix channel `#jenkins-infra` mentioning this issue and this item is enough: they will own the backports
36
35
37
36
-[ ] Create a pull request to update [bom](https://github.com/jenkinsci/bom) to the weekly version that will be the base of the release line (and strike this out for new point release).
38
37
Assure that the [bom-weekly version number](https://github.com/jenkinsci/bom/blob/master/sample-plugin/pom.xml#L17) is already testing the base of the release line or a version newer than the base of the release line.
Copy file name to clipboardExpand all lines: Jenkinsfile.d/core/package
+8-28Lines changed: 8 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -62,11 +62,6 @@ pipeline {
62
62
description: 'Enable Windows Packaging',
63
63
name: 'WINDOWS_PACKAGING_ENABLED'
64
64
)
65
-
booleanParam(
66
-
defaultValue: false,
67
-
description: 'Force bootstrap (cleanup + initialization from production) of the packages staging environment if data from previous staged build is present.',
68
-
name: 'FORCE_STAGING_BOOTSTRAP_PARAM'
69
-
)
70
65
booleanParam(
71
66
defaultValue: false,
72
67
description: 'Select this checkbox if you want to disable promotion to production (e.g. only publish to staging).',
// Using HTTPS with no credentials - https://github.com/jenkins-infra/helpdesk/issues/4909 - need a GH app if rate limited or need to write things to git
// Using HTTPS with no credentials - https://github.com/jenkins-infra/helpdesk/issues/4909 - need a GH app if rate limited or need to write things to git
- Start-Sleep -s 2147483 # We must be sure that the process used by the container doesn't stop before the Jenkins job and second is not greater than 2147483
Copy file name to clipboardExpand all lines: README.adoc
+25-4Lines changed: 25 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -365,6 +365,8 @@ All steps need to be done twice: Once for weekly, once for LTS.
365
365
366
366
==== Staging (before release day)
367
367
368
+
===== Maven Artifacts
369
+
368
370
To stage the Maven artifacts, trigger the generic Release link:https://release.ci.jenkins.io/job/core/job/release/[job] from the appropriate branch like `security-stable-2.303.2`.
369
371
370
372
To do that, follow these steps:
@@ -377,16 +379,35 @@ To do that, follow these steps:
377
379
... `MAVEN_REPOSITORY_NAME` set to `unused` as we already define it in the release profile file, which overrides the job parameter
378
380
... `VALIDATION_ENABLED` set to true if the validation stage should run
379
381
380
-
==== Publishing (on release day)
382
+
===== Packages
381
383
382
-
. To create and publish packages, trigger the generic Packaging job link:https://release.ci.jenkins.io/job/core/job/package/[job] from the appropriate branch like `security-stable-2.303.2` with correct parameters
384
+
. To create and stage packages (except Docker images), trigger the generic Packaging job link:https://release.ci.jenkins.io/job/core/job/package/[job] from the appropriate branch like `security-stable-2.303.2` with correct parameters
383
385
.. `RELEASE_PROFILE` set to `security`
386
+
.. `JENKINS_VERSION` set to `unused` same reason as before
384
387
.. `RELEASE_GIT_BRANCH` set to `unused` same reason as before
385
388
.. `MAVEN_REPOSITORY_NAME` set to `unused` same reason as before
386
-
.. `MAVEN_REPOSITORY_PRODUCTION_NAME` set to `unused`
389
+
.. `MAVEN_REPOSITORY_PRODUCTION_NAME` set to `unused` same reason as before
390
+
.. `MAVEN_STAGING_REPOSITORY_PROMOTION_ENABLED` set to false (manually done by publishing-tool in a parallel process)
391
+
.. `GIT_STAGING_REPOSITORY_PROMOTION_ENABLED` set to false (manually merged by security team)
392
+
.. `VALIDATION_ENABLED` set to true (we want a summary of what need to be done at the beginning)
393
+
.. `WINDOWS_PACKAGING_ENABLED` set to true (we want to generate and stage Windows package along with other packages)
394
+
.. `ONLY_STAGING_PARAM` set to true (we only want to stage, not publish)
395
+
.. `ONLY_PROMOTION_PARAM` set to false (we only want to stage, not publish)
396
+
397
+
==== Publishing (on release day)
398
+
399
+
. To publish packages from staging, trigger the generic Packaging job link:https://release.ci.jenkins.io/job/core/job/package/[job] from the appropriate branch like `security-stable-2.303.2` with correct parameters
400
+
.. `RELEASE_PROFILE` set to `security`
401
+
.. `JENKINS_VERSION` set to `unused` same reason as before
402
+
.. `RELEASE_GIT_BRANCH` set to `unused` same reason as before
403
+
.. `MAVEN_REPOSITORY_NAME` set to `unused` same reason as before
404
+
.. `MAVEN_REPOSITORY_PRODUCTION_NAME` set to `unused` same reason as before
387
405
.. `MAVEN_STAGING_REPOSITORY_PROMOTION_ENABLED` set to false (manually done by publishing-tool in a parallel process)
388
406
.. `GIT_STAGING_REPOSITORY_PROMOTION_ENABLED` set to false (manually merged by security team)
389
-
.. `VALIDATION_ENABLED` set to true
407
+
.. `VALIDATION_ENABLED` set to true (we want a summary of what need to be done at the beginning)
408
+
.. `WINDOWS_PACKAGING_ENABLED` set to **false** (no package generation)
409
+
.. `ONLY_STAGING_PARAM` set to **false** (we don't want to stage anything)
410
+
.. `ONLY_PROMOTION_PARAM` set to **true** (we only want to publish)
0 commit comments