Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.1, 2.0.2, 2.0.3
    • Fix Version/s: 2.0.4
    • Component/s: Maven3
    • Labels:
      None
    • Environment:

      Jenkins version 1.423, artifactory-plugin 2.0.3 running on SuSe Linux (64) , build running on slave node (also SuSe Linux (64)).

      Description

      Building on a dumb slave fails if a enable "Deploy artifacts to Artifactory". The error I get is:

      ... 
      [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/data/builder/node/workspace/my-job/2.0.3 -cp /var/buildnode/maven3-agent.jar:/var/buildnode/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/buildnode/tools/maven-3-latest /var/buildnode/slave.jar /var/buildnode/maven3-interceptor.jar 53699 
      Exception in thread "main" java.io.FileNotFoundException: /data/builder/node/workspace/my-job/2.0.3
      	at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336)
      	at org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247)
      	at org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135)
      	at org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132)
      	at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:106)
      	at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:63)
      ERROR: Failed to launch Maven. Exit code = 1
      ...
      

      When I run this build on the master node, there is no problem. The corresponding (correct) log-part is:

      ...
      [my-job] $ java -client -Xms256m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Dm3plugin.lib=/opt/jenkins/plugins/artifactory/WEB-INF/lib -cp /var/buildnode/maven3-agent.jar:/var/buildnode/tools/maven-3-latest/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/buildnode/tools/maven-3-latest /var/buildnode/slave.jar /var/buildnode/maven3-interceptor.jar 53699 
      <===[JENKINS REMOTING CAPACITY]===>
      channel started
      Executing Maven:  -B -f /opt/jenkins/jobs/my-job/workspace/pom.xml clean install
      [INFO] Scanning for projects
      ...
      

      Notice the different -Dm3plugin.lib setting. On the remote slave the /data/builder/node/workspace/my-job/2.0.3 does not exist.

      I also created this issue on Jenkins-ci (see https://issues.jenkins-ci.org/browse/JENKINS-10259) I think this is really a plugin problem.

        Attachments

        1. my-job-config.xml
          4 kB
        2. slave-config.xml
          2 kB
        3. slave-perimeter.log
          5 kB
        4. slave-perimeter.log
          5 kB

          Issue Links

            Activity

              People

              • Assignee:
                yossis Yossi Shaul
                Reporter:
                ikanters Ivar Kanters
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: