James King
James King

Reputation: 2445

Maven/Jenkins - trouble running Maven from Jenkins

So I have a project that runs Jenkins, which calls Maven, which calls Ant (dont ask why) which runs a series of JMeter tests.

I know the Ant and JMeter stuff works fine. The issue Im having is when trying to add Maven to the mix.

I have it calling the pom.xml which simple references the ant build.xml file. the error I get is below:

Started by user anonymous
Building in workspace C:\Users\MURPHYA1\.jenkins\jobs\JMeter-Running-Mavin\workspace
Parsing POMs
Discovered a new module JMeter-Running-Maven:JMeter-Running-Maven JMeter-Running-Maven
Modules changed, recalculating dependency graph
[workspace] $ java -cp "C:\Users\MURPHYA1\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-agent-1.4.jar;C:\Users\MURPHYA1\Desktop\Code samples\apache-maven-3.1.0-bin\apache-maven-3.1.0\boot\plexus-classworlds-2.4.2.jar" jenkins.maven3.agent.Maven31Main "C:\Users\MURPHYA1\Desktop\Code samples\apache-maven-3.1.0-bin\apache-maven-3.1.0" C:\Users\MURPHYA1\.jenkins\war\WEB-INF\lib\remoting-2.30.jar C:\Users\MURPHYA1\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-interceptor-1.4.jar C:\Users\MURPHYA1\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.4.jar 56391
<===[JENKINS REMOTING CAPACITY]===>channel started
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
Executing Maven:  -B -f C:\Users\MURPHYA1\.jenkins\jobs\JMeter-Running-Mavin\workspace\pom.xml run
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - Scanning for projects...
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects...
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener -                                                                         
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - ------------------------------------------------------------------------
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - Building JMeter-Running-Maven 1.0-SNAPSHOT
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - ------------------------------------------------------------------------
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger -                                                                         
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Building JMeter-Running-Maven 1.0-SNAPSHOT
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - ------------------------------------------------------------------------
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - BUILD FAILURE
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - ------------------------------------------------------------------------
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - Total time: 0.749s
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - Finished at: Wed Aug 07 11:10:02 BST 2013
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - Final Memory: 3M/61M
[pool-1-thread-1] INFO hudson.maven.Maven3Builder$MavenExecutionListener - ------------------------------------------------------------------------
[JENKINS] Archiving C:\Users\MURPHYA1\.jenkins\jobs\JMeter-Running-Mavin\workspace\pom.xml to C:\Users\MURPHYA1\.jenkins\jobs\JMeter-Running-Mavin\modules\JMeter-Running-Maven$JMeter-Running-Maven\builds\2013-08-07_11-09-52\archive\JMeter-Running-Maven\JMeter-Running-Maven\1.0-SNAPSHOT\JMeter-Running-Maven-1.0-SNAPSHOT.pom
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - BUILD FAILURE
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Total time: 4.863s
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Finished at: Wed Aug 07 11:10:06 BST 2013
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Final Memory: 3M/61M
[pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
channel stopped
Finished: FAILURE

and my pom.xml is below:

<project>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>JMeter-Running-Maven</artifactId>
  <groupId>JMeter-Running-Maven</groupId>
  <version>1.0-SNAPSHOT</version>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <version>1.7</version>
        <executions>
          <execution>
            <phase>generate-sources</phase>
            <configuration>
              <tasks>           
                <ant antfile="${basedir}/build.xml">
                    <target name="prepare-JMeter-Running-Maven" />
                </ant>
              </tasks>
            </configuration>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</project>

Is anyone able to point out where I have gone wrong? Thanks

UPDATE

I am running this off a clients VDI machine, which I has having issues running commands such as mvn install, which was giving me errors such as connection refused:forbidden and timed out. Do you think this is the issue, or is my pom.xml just not correct?

Upvotes: 1

Views: 1215

Answers (1)

James King
James King

Reputation: 2445

So the issue was that the vdi was blocking me downloading the relevant jar and pom files. So what I did was run the task on my local machine, copied the files across to my vdi repo and for the jar files, I registered them with the following maven command:

mvn install:install-file -Dfile=.\lib\com.ibm.mq.jar -DgroupId=com.ibm.mq -DartifactId=WebsphereMQClassesForJava -Dversion=7.0.1.5 -Dpackaging=jar

Upvotes: 1

Related Questions