search

jenkinsci / opentelemetry-plugin

Monitor and observe Jenkins with OpenTelemetry.
https://plugins.jenkins.io/opentelemetry/
Apache License 2.0
100 stars 53 forks source link

chore(deps): bump org.jenkins-ci.plugins:plugin from 4.88 to 5.2 #968

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 1 month ago

Bumps org.jenkins-ci.plugins:plugin from 4.88 to 5.2.

Release notes

Sourced from org.jenkins-ci.plugins:plugin's releases.

5.2

📦 Dependency updates

5.1

🐛 Bug fixes

📝 Documentation updates

  • Update version of parent pom for Java 17 being required (#1030) @​timja

📦 Dependency updates

  • Bump org.jenkins-ci.main:jenkins-test-harness from 2299.v7e8d22e797d3 to 2307.v10e5d0701b_e5 (#1031) @​dependabot

5.0

💥 Breaking changes

Since 5.0 the plugin parent pom now requires a minimum jenkins.version of 2.479 and to be run with Java 17

🚀 New features and improvements

🐛 Bug fixes

📝 Documentation updates

  • Add documentation for frontend integration with maven build (#1016) @​timja

✍ Other changes

... (truncated)

Commits
  • bbd9055 [maven-release-plugin] prepare release plugin-5.2
  • 4b93408 Bump org.jenkins-ci.tools:maven-hpi-plugin from 3.58 to 3.59 (#1041)
  • 17f0720 Bump io.jenkins.tools.maven:license-maven-plugin (#1040)
  • 87b730a Bump io.jenkins.tools.maven:stapler-maven-plugin (#1039)
  • 56bed1d Bump org.mockito:mockito-bom from 5.14.1 to 5.14.2 (#1038)
  • bd2fa32 Bump org.jenkins-ci.main:jenkins-test-harness (#1037)
  • ee417f7 Bump maven-surefire-plugin.version from 3.5.0 to 3.5.1 (#1036)
  • 6167575 Bump org.junit:junit-bom from 5.11.1 to 5.11.2 (#1035)
  • 6d03675 [maven-release-plugin] prepare for next development iteration
  • 1ef856e [maven-release-plugin] prepare release plugin-5.1
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
cyrille-leclerc commented 2 weeks ago

@kuisathaverat I propose to wait a bit before bumping the Jenkins requirement to v2.479. WDYT?

kuisathaverat commented 2 weeks ago

I propose to wait a bit before bumping the Jenkins requirement to v2.479. WDYT?

I was waiting for that version, it drops support for Java 11

https://github.com/jenkinsci/opentelemetry-plugin/pull/978

cyrille-leclerc commented 2 weeks ago

We have lost the usage stats. Do we know if Jenkins admins struggle to bump to their JVMs to Java 17?

kuisathaverat commented 2 weeks ago

We have lost the usage stats.

WDYM?

Do we know if Jenkins admins struggle to bump to their JVMs to Java 17?

We can ask @MarkEWaite, but I do not see many messages in the user groups about updating to Java 17. It's getting easier with the time.

kuisathaverat commented 2 weeks ago

BTW if you are agree we can merge https://github.com/jenkinsci/opentelemetry-plugin/pull/978

kuisathaverat commented 2 weeks ago

@dependabot rebase

dependabot[bot] commented 2 weeks ago

Looks like org.jenkins-ci.plugins:plugin is up-to-date now, so this is no longer needed.

MarkEWaite commented 2 weeks ago

We have lost the usage stats.

WDYM?

For about 6 months, we did not have updates to the plugin installation statistics and the JVM adoption metrics . That was fixed within the last few days, thanks to Andrew Bayer and Kohsuke Kawaguchi.

Do we know if Jenkins admins struggle to bump to their JVMs to Java 17?

JVM adoption graph looks very good. Continued very good progress adopting Java 17 among Jenkins users. The count of Java 17 (115k) and Java 21 (27k) installations exceeds the count of Java 11 (82k) and Java 8 (50k) and installations.

JVMs By Date

We can ask @MarkEWaite, but I do not see many messages in the user groups about updating to Java 17. It's getting easier with the time.

We're not seeing any significant issues with adoption of Java 17 but I think that it may still be too early for the users of the Open Telemetry plugin. The installation statistics show that only 17% of the users are on 2.475 or newer. That is the first Jenkins weekly that requires Jakarta EE 9 and Spring Security 6. Installation statistics do not include 2.479.1 yet (released 30 Oct 2024), but I suspect that it is still too early to lock out users that are running older Jenkins LTS versions.

Upgrading to require Jenkins 2.479.1 requires steps like: