Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove 2.361.x support #2121

Merged
merged 5 commits into from
May 30, 2023
Merged

Remove 2.361.x support #2121

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
fabd5a5
Use 2.387.x in example
MarkEWaite May 28, 2023
dbf2fbd
Drop 2.361.x from plugin BOM
MarkEWaite May 28, 2023
00eaa28
Explain why we rarely keep more than 3 LTS lines
MarkEWaite May 30, 2023
72fea94
Better phrasing
MarkEWaite May 30, 2023
c9be463
Merge branch 'master' into drop-2.361.x
MarkEWaite May 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ If you are interested in a Bill of Materials for Jenkins core components, see [t
After selecting your plugin’s LTS baseline:

```xml
<jenkins.version>2.361.4</jenkins.version>
<jenkins.version>2.387.3</jenkins.version>
```

just import the [latest BOM](https://github.com/jenkinsci/bom/releases) from that line:
Expand All @@ -24,7 +24,7 @@ just import the [latest BOM](https://github.com/jenkinsci/bom/releases) from tha
<dependencies>
<dependency>
<groupId>io.jenkins.tools.bom</groupId>
<artifactId>bom-2.361.x</artifactId>
<artifactId>bom-2.387.x</artifactId>
<version>…</version>
<scope>import</scope>
<type>pom</type>
Expand Down Expand Up @@ -186,9 +186,10 @@ The CI build (or just `mvn test -P2.nnn.x`) will fail if some managed plugins ar
[This script](https://gist.github.com/jglick/0a85759ea65f60e107ac5a85a5032cae)
is a handy way to find the most recently released plugin version compatible with a given line,
according to the `jenkins-infra/update-center2`.
The UC currently maintains releases for the [past 400 days](https://groups.google.com/g/jenkins-infra/c/LTrRUqkgeQA/m/UmQMD5gDAgAJ)
so it is reasonable to retire BOMs for lines older than that,
or otherwise when the number of accumulated version overrides becomes large.

The [developer documentation](https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/) recommends the last releases of each of the previous two LTS baselines.
BOMs for the current LTS release and two prior LTS releases are typically retained.
BOMs older than the two prior LTS releases will generally be retired in order to better manage evaluation costs and maintenance efforts.

## Releasing

Expand Down
42 changes: 0 additions & 42 deletions bom-2.361.x/pom.xml
View file
Open in desktop

This file was deleted.

1 change: 0 additions & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,6 @@
<module>bom-2.401.x</module>
<module>bom-2.387.x</module>
<module>bom-2.375.x</module>
<module>bom-2.361.x</module>
<module>sample-plugin</module>
</modules>
<scm child.scm.connection.inherit.append.path="false" child.scm.developerConnection.inherit.append.path="false" child.scm.url.inherit.append.path="false">
Expand Down
7 changes: 0 additions & 7 deletions sample-plugin/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -693,12 +693,5 @@
<jenkins.version>2.375.4</jenkins.version>
</properties>
</profile>
<profile>
<id>2.361.x</id>
<properties>
<bom>2.361.x</bom>
<jenkins.version>2.361.4</jenkins.version>
</properties>
</profile>
</profiles>
</project>