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.

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

[JENKINS-66326] Prepare SCM Sync Configuration for core Guava upgrade #74

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

basil
Copy link
Member

@basil basil commented Aug 21, 2021

Downstream of #70. See JENKINS-66326 and JENKINS-65988. Jenkins core is using Guava 11.0.1, which was released on January 9, 2012. Jenkins core would like to upgrade to Guava 30.1.1, which was released on March 19, 2021. Plugins must be prepared to be compatible with both Guava 11.0.1 and Guava 30.1.1 in advance of this core transition.

In particular, this plugin has been identified as using the following methods which have been removed in the latest version of Guava:

  • com/google/common/io/ByteStreams#getChecksum
  • com/google/common/io/ByteStreams#newInputStreamSupplier
  • com/google/common/io/Files#getChecksum

These methods existed in Guava 11.0.1 but have been removed in recent versions.

To facilitate the Jenkins core transition, this plugin must be prepared and released such that it works with both Guava 11.0.1 and latest. This PR rewrites the relevant code to avoid the use of Guava and use native Java Platform functionality instead.

CC @guipal @rodrigc

@basil
Copy link
Member Author

basil commented Sep 26, 2021

@guipal @rodrigc Would it be possible to take a look at this PR?

@basil
Copy link
Member Author

basil commented Oct 23, 2021

@guipal @rodrigc Gentle ping. It would be nice to get this PR merged and released to facilitate the upcoming Guava upgrade in Jenkins core (JEP-233).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants