949716 - Please bump maven to 3.1.1 on ci.mozilla.org

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Nick Alexander :nalexander [he/him]]

android-sync's local repositories have been updated, but ci.mozilla.org's Jenkins job fails:

...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project android-sync-app: failed to get report for org.apache.maven.plugins:maven-surefire-report-plugin: Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.8.0:generate-sources (default-generate-sources) on project android-sync-app: The plugin com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.8.0 requires Maven version 3.1.1 -> [Help 1]
...

Can we get a maven version bump, please?

Comment 1

[Richard Newman [:rnewman]]

Note that 3.1.1 was released at the end of September, so it's had a while to bake.

Comment 2

[Brandon Burton [:solarce]]

The maven2 install appears to be a custom rpm someone built and put in our internal repository.

There doesn't seem to be an official maven 3 rpm so I've built one and installed

The maven 3 binary is located at /opt/maven/bin/mvn

[[e-mail]1 ~]# /opt/maven/bin/mvn
mvn       mvnDebug  mvnyjp
[[e-mail]1 ~]# /opt/maven/bin/mvn -v
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 08:22:22-0700)
Maven home: /opt/maven
Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0.22.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-358.6.2.el6.x86_64", arch: "amd64", family: "unix"

Comment 3

[Nick Alexander :nalexander [he/him]]

(In reply to Brandon Burton [:solarce] from comment #2)
> The maven2 install appears to be a custom rpm someone built and put in our
> internal repository.
> 
> There doesn't seem to be an official maven 3 rpm so I've built one and
> installed
> 
> The maven 3 binary is located at /opt/maven/bin/mvn
> 
> [[e-mail]1 ~]# /opt/maven/bin/mvn
> mvn       mvnDebug  mvnyjp
> [[e-mail]1 ~]# /opt/maven/bin/mvn -v
> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
> 08:22:22-0700)
> Maven home: /opt/maven
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0.22.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-358.6.2.el6.x86_64", arch: "amd64",
> family: "unix"

Sorry for the delay verifying this, but I'm still having trouble:

+ echo 'Android home is /var/lib/jenkins/tools/android-sdk'
Android home is /var/lib/jenkins/tools/android-sdk
+ /opt/maven/bin/mvn -v
Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/3.0.x-latest
Java version: 1.6.0_28, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-358.6.2.el6.x86_64", arch: "amd64", family: "unix"
Parsing POMs

See the log at https://ci.mozilla.org/job/sync-android/1823/consoleFull

And then the actual Jenkins job uses some Jenkins/Maven plug-in that doesn't let me set the path.  Any thoughts?

Comment 4

[Brandon Burton [:solarce]]

(In reply to Nick Alexander :nalexander from comment #3)
> (In reply to Brandon Burton [:solarce] from comment #2)
> > The maven2 install appears to be a custom rpm someone built and put in our
> > internal repository.
> > 
> > There doesn't seem to be an official maven 3 rpm so I've built one and
> > installed
> > 
> > The maven 3 binary is located at /opt/maven/bin/mvn
> > 
> > [[e-mail]1 ~]# /opt/maven/bin/mvn
> > mvn       mvnDebug  mvnyjp
> > [[e-mail]1 ~]# /opt/maven/bin/mvn -v
> > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
> > 08:22:22-0700)
> > Maven home: /opt/maven
> > Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> > Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0.22.x86_64/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "2.6.32-358.6.2.el6.x86_64", arch: "amd64",
> > family: "unix"
> 
> Sorry for the delay verifying this, but I'm still having trouble:
> 
> + echo 'Android home is /var/lib/jenkins/tools/android-sdk'
> Android home is /var/lib/jenkins/tools/android-sdk
> + /opt/maven/bin/mvn -v
> Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
> Maven home:
> /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/3.0.x-latest
> Java version: 1.6.0_28, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-358.6.2.el6.x86_64", arch: "amd64",
> family: "unix"
> Parsing POMs
> 
> See the log at https://ci.mozilla.org/job/sync-android/1823/consoleFull
> 
> And then the actual Jenkins job uses some Jenkins/Maven plug-in that doesn't
> let me set the path.  Any thoughts?

Apparently Jenkins manages its own Maven installs as well and the 3.0.4 was from there.

I've updated the Jenkins config to install 3.1.1 in its install as well

Maven home: /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/3.1.x-latest

https://ci.mozilla.org/job/sync-android/1824/console ran with 3.1.1 failed because now we need to bump maven-site-plugin to 3.3 in pom.xml

I've submitted a PR for this, https://github.com/mozilla-services/android-sync/pull/373

Once that's merged I think the build should run again

Comment 5

[Richard Newman [:rnewman]]

Next problem:

[EnvInject] - [ERROR] - Can't mask global password :Job type hudson.maven.MavenModule@4abe9185[sync-android/org.mozilla.gecko:android-sync][sync-android/org.mozilla.gecko:android-sync][relativePath:] is not supported

Comment 6

[Brandon Burton [:solarce]]

(In reply to Richard Newman [:rnewman] from comment #5)
> Next problem:
> 
> [EnvInject] - [ERROR] - Can't mask global password :Job type
> hudson.maven.MavenModule@4abe9185[sync-android/org.mozilla.gecko:android-
> sync][sync-android/org.mozilla.gecko:android-sync][relativePath:] is not
> supported

That error was present even in working builds, like https://ci.mozilla.org/job/sync-android/1811/console and doesn't appear to be one that causes the build to fail, the failing error in https://ci.mozilla.org/job/sync-android/1826/console is

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project android-sync-app: failed to get report for org.apache.maven.plugins:maven-surefire-report-plugin: Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.8.0:generate-sources (default-generate-sources) on project android-sync-app: Execution default-generate-sources of goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.8.0:generate-sources failed: Invalid SDK: Platform/API level 16 not available. This command should give you all you need:
[ERROR] /var/lib/jenkins/tools/android-sdk/tools/android update sdk --no-ui --obsolete --force

I ran that command to update the android-sdk, which took a while to download the Internet, but it finished

Now the build is dying in https://ci.mozilla.org/job/sync-android/1827/console with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project android-sync-app: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on project android-sync-instrumentation: Could not resolve dependencies for project org.mozilla.gecko:android-sync-instrumentation:apk:1: Could not find artifact org.mozilla.gecko:android-sync-app:apk:1 in android-sync-mvn-repo (https://raw.github.com/mozilla-services/android-sync/mvn-repo/) -> [Help 1]

Which seems like something you need to fix in that repo?

I should note we're getting pretty far outside my familiarity zone, I haven't touched maven in 2007 before today :)
[ERROR] -> [Help 1]

Comment 7

[Nick Alexander :nalexander [he/him]]

Looks like we've hit a legitimate issue:

https://issues.jenkins-ci.org/browse/JENKINS-13709
https://github.com/jenkinsci/dom4j/pull/4

I'll try to work around it by not building the site target for a while.

Comment 8

[Brandon Burton [:solarce]]

(In reply to Nick Alexander :nalexander from comment #7)
> Looks like we've hit a legitimate issue:
> 
> https://issues.jenkins-ci.org/browse/JENKINS-13709
> https://github.com/jenkinsci/dom4j/pull/4
> 
> I'll try to work around it by not building the site target for a while.

Nice find! I added a '+1, plz' merge on the PR that's supposed to fix it

Comment 9

[Nick Alexander :nalexander [he/him]]

(In reply to Nick Alexander :nalexander from comment #7)
> Looks like we've hit a legitimate issue:
> 
> https://issues.jenkins-ci.org/browse/JENKINS-13709
> https://github.com/jenkinsci/dom4j/pull/4
> 
> I'll try to work around it by not building the site target for a while.

So changing to |clean compile test| instead of |clean site| has at least got the tests running, which is most of what we care about.  Let's leave this for a while, and if we find we've lost valuable information we'll try to bump Maven again at a later date and hope this issue is resolved.