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

Update plugins #37

Merged
merged 24 commits into from Dec 7, 2018
Merged

Update plugins #37

merged 24 commits into from Dec 7, 2018

Conversation

batmat
Copy link
Member

@batmat batmat commented Dec 2, 2018

Just made a pass of versions:display-plugins-updates.

Successful downstream PR builds with timestamped SNAPSHOT on the following components (1.51-20181206.212314-4):

Output was:

INFO] The following plugin updates are available:
[INFO]   io.jenkins.tools.incrementals:incrementals-maven-plugin  1.0-beta-5 -> 1.0-beta-7
[INFO]   maven-checkstyle-plugin ............................... 2.17 -> 3.0.0
[INFO]   maven-clean-plugin ................................... 3.0.0 -> 3.1.0
[INFO]   maven-dependency-plugin .............................. 3.0.2 -> 3.1.1
[INFO]   maven-deploy-plugin ............................... 2.8.2 -> 3.0.0-M1
[INFO]   maven-enforcer-plugin .......................... 3.0.0-M1 -> 3.0.0-M2
[INFO]   maven-help-plugin .................................... 3.0.1 -> 3.1.0
[INFO]   maven-idea-plugin ........................... 2.2 -> 2.3-atlassian-10
[INFO]   maven-install-plugin .............................. 2.5.2 -> 3.0.0-M1
[INFO]   maven-jar-plugin ..................................... 3.0.2 -> 3.1.0
[INFO]   maven-jxr-plugin ....................................... 2.5 -> 3.0.0
[INFO]   maven-pmd-plugin ...................................... 3.8 -> 3.11.0
[INFO]   maven-project-info-reports-plugin ...................... 2.9 -> 3.0.0
[INFO]   maven-remote-resources-plugin .......................... 1.5 -> 1.6.0
[INFO]   maven-resources-plugin ............................... 3.0.2 -> 3.1.0
[INFO]   maven-site-plugin ...................................... 3.7 -> 3.7.1
[INFO]   maven-surefire-plugin .............................. 2.20 -> 3.0.0-M1
[INFO]   maven-surefire-report-plugin ....................... 2.20 -> 3.0.0-M1
[INFO]   maven-war-plugin ..................................... 3.1.0 -> 3.2.2
[INFO]   org.codehaus.cargo:cargo-maven2-plugin ............... 1.1.2 -> 1.7.0
[INFO]   org.codehaus.mojo:gwt-maven-plugin ................. 2.3.0-1 -> 2.8.2
[INFO]   org.codehaus.mojo:versions-maven-plugin .................. 2.5 -> 2.7
[INFO]   org.codehaus.mojo:xml-maven-plugin ..................... 1.0 -> 1.0.2
[INFO]   org.jenkins-ci.tools:maven-hpi-plugin .................... 2.3 -> 2.7
[INFO]   org.jvnet.maven-antrun-extended-plugin:maven-antrun-extended-plugin  1.42 -> 1.43
[INFO]   org.mortbay.jetty:maven-jetty-plugin ........... 6.1.26 -> 7.0.0.pre5

@olamy
Copy link
Member

olamy commented Dec 3, 2018

do we really use idea or cargo or gwt plugins? We can probably get rid of those?

@jtnord
Copy link
Member

jtnord commented Dec 3, 2018

the deploy plugin scares me a little bit and I think would be a blocker for the CERT team

https://issues.apache.org/jira/browse/MDEPLOY-244

Copy link
Member

@jtnord jtnord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@batmat
Copy link
Member Author

batmat commented Dec 3, 2018

Fine by me. This PR also definitely was intended to actually gather that feedback and still try to attempt as many components as we can. Going to revert m-deploy-p and Surefire related bumps and ask again for review. We'll reconsider these possibly later.

This reverts commit a86f937.

# Conflicts:
#	pom.xml
This reverts commit 9cc7633.
@batmat
Copy link
Member Author

batmat commented Dec 3, 2018

@oleg-nenashev @jtnord I reverted m-surefire-*-p and m-deploy-p. Care to re-review?

Also pushed a new timestamped SNAPSHOT 1.51-20181203.164412-3 into jenkinsci/jenkins#3785 to test its behavior.

Thanks

Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I literally have no idea what is going to blow up there. Looks good, 🚢 🇮🇹

Speaking seriously, we have enough time to cleanup the things before the next LTS baseline if something goes wrong. +1 from me from merging once there are downstream pull requests with the update pickup to...

  • Jenkins Core
  • Remoting
  • Winstone
  • Plugin Compat Tester

It should give us enough blow-up coverage taking the recent experience with upgrades

@batmat batmat requested review from oleg-nenashev and removed request for oleg-nenashev December 6, 2018 10:14
Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Worth retrying several builds with checkstyle/coverage profiles on Java 8 and Java 11 after merging

@batmat
Copy link
Member Author

batmat commented Dec 6, 2018

All upstream PRs filed @oleg-nenashev. We'll see how they go.

@batmat
Copy link
Member Author

batmat commented Dec 7, 2018

All downstream PRs successful. Merging given the review approvals.

@batmat batmat merged commit 84ad44d into jenkinsci:master Dec 7, 2018
@batmat batmat deleted the update-plugins branch December 7, 2018 13:14
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.

None yet

5 participants