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

Bump Maven to 3.6.3 as builder for PCT Dockerfile #277

Merged
merged 5 commits into from
Mar 22, 2021

Conversation

imonteroperez
Copy link
Contributor

  • Let's update the Maven version for PCT Dockerfile
  • Previous to this change some plugins are not tested properly, such as artifact-manager-s3 using Maven 3.6.0
09:22:00  Failed while enforcing RequireUpperBoundDeps. The error(s) are [
09:22:00  Require upper bound dependencies error for org.slf4j:slf4j-api:1.7.26 paths to dependency are:
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.testcontainers:testcontainers:1.15.2
09:22:00      +-org.slf4j:slf4j-api:1.7.26
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-io.findify:s3mock_2.12:0.2.5
09:22:00      +-com.typesafe.scala-logging:scala-logging_2.12:3.8.0
09:22:00        +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.30
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.testcontainers:testcontainers:1.15.2
09:22:00      +-com.github.docker-java:docker-java-api:3.2.7
09:22:00        +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.30
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.testcontainers:testcontainers:1.15.2
09:22:00      +-com.github.docker-java:docker-java-transport-zerodep:3.2.7
09:22:00        +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.25
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.jenkins-ci.main:jenkins-core:2.235.2
09:22:00      +-org.slf4j:jcl-over-slf4j:1.7.26
09:22:00        +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.25
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.jenkins-ci.main:jenkins-core:2.235.2
09:22:00      +-org.slf4j:log4j-over-slf4j:1.7.26
09:22:00        +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.25
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.jenkins-ci.main:jenkins-war:2.235.2
09:22:00      +-org.slf4j:slf4j-jdk14:1.7.26
09:22:00        +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.25
09:22:00  and
09:22:00  +-io.jenkins.plugins:artifact-manager-s3:1.13
09:22:00    +-org.jenkins-ci.main:jenkins-war:2.235.2
09:22:00      +-org.jenkins-ci.modules:sshd:2.6
09:22:00        +-org.apache.sshd:sshd-core:1.7.0
09:22:00          +-org.slf4j:slf4j-api:1.7.26 (managed) <-- org.slf4j:slf4j-api:1.7.25
  • After this PR, plugins are properly evaluated/tested by the PCT as expected (tested with Maven 3.6.2 and Maven 3.6.3)

Copy link
Member

@jglick jglick left a comment

Choose a reason for hiding this comment

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

Yes please, we should not be running anything other than the current Maven release on any infrastructure.

While you are here please replace

private static final String DISABLE_DOWNLOAD_LOGS = "-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn";
with -ntp to follow up from #216.

@imonteroperez
Copy link
Contributor Author

Yes please, we should not be running anything other than the current Maven release on any infrastructure.

While you are here please replace

private static final String DISABLE_DOWNLOAD_LOGS = "-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn";

with -ntp to follow up from #216.

Updated in 838cc64

@imonteroperez
Copy link
Contributor Author

@jglick any hint about ci/dockercloud-stage check failure? link redirects me to a 404 😕

@jglick
Copy link
Member

jglick commented Mar 19, 2021

I guess somebody set up Docker automated builds at some point. It is a 404 for me too. Maybe the repo owner can see it.

…en/ExternalMavenRunner.java

Co-authored-by: Jesse Glick <jglick@cloudbees.com>
Copy link
Member

@jglick jglick left a comment

Choose a reason for hiding this comment

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

I think you need to patch

TEST_JDK_HOME=${TEST_JAVA_ARGS:-"/usr/lib/jvm/java-${JDK_VERSION:-8}-openjdk-amd64"}

$ docker run --rm --entrypoint bash maven:3.6.0-jdk-8 -c 'realpath $(which java)'
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
$ docker run --rm --entrypoint bash maven:3.6.3-jdk-8 -c 'realpath $(which java)'
/usr/local/openjdk-8/bin/java

@@ -157,7 +157,7 @@ mkdir -p "${PCT_OUTPUT_DIR}"
###
# Determine if we test the plugin against another JDK
###
TEST_JDK_HOME=${TEST_JAVA_ARGS:-"/usr/lib/jvm/java-${JDK_VERSION:-8}-openjdk-amd64"}
TEST_JDK_HOME=${TEST_JAVA_ARGS:-"/usr/local/openjdk-${JDK_VERSION:-8}"}
Copy link
Member

Choose a reason for hiding this comment

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

AFAICT not going to work for JDK 11 as installed in

mv jdk-11.0.1/ /usr/lib/jvm/java-11-openjdk-amd64 && \

Copy link
Member

Choose a reason for hiding this comment

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

Cannot run program "/usr/local/openjdk-11/bin/java": error=2, No such file or directory

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@imonteroperez imonteroperez merged commit 230b644 into master Mar 22, 2021
@jglick jglick deleted the maven-bump-3.6.3 branch March 22, 2021 19:03
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.

7 participants