Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21423

Matrix jobs consistently fail when run concurrently

      Jenkins 1.518

      We use matrix jobs for deployments and have noticed matrix jobs always fail when we disable Run each configuration sequentially. The failure appears on random hosts.

      • Our jobs assemble a zip file which is SCP'd to a target host and inflated.

      Problem seen and important points

      • The wagon-maven-plugin:1.0-beta-4:upload step runs and appears to SCP the zip file to the target host.
      • We can see the zip file in the Jenkins workspace directory for the axis.
      • The zip file is not found on the target host and the deploy fails.
      • The same matrix job succeeds when run sequentially.
      • We see the same behavior with all matrix jobs.

      Additional observations

      • This problem does not appear resource-related because we can run non-matrix jobs concurrently and they succeed.
      • The same bad behavior for matrix jobs occurs on single and multi-node Jenkins servers. Thus it isn't a slave problem.

          [JENKINS-21423] Matrix jobs consistently fail when run concurrently

          Oleg Nenashev added a comment - - edited

          Seems the issue is mostly related to Maven plugin.
          What version do you use?

          I suppose you should re-check the issue with Maven-2.1 plugin, which uses a newer Maven Wagon version (see JENKINS-11164)

          Oleg Nenashev added a comment - - edited Seems the issue is mostly related to Maven plugin. What version do you use? I suppose you should re-check the issue with Maven-2.1 plugin, which uses a newer Maven Wagon version (see JENKINS-11164 )

          S Stack added a comment -

          @Oleg, thank you very much.

          • We are running Jenkins 1.518 using Maven Project Plugin 1.511.
          • Regarding Maven 2.1, update center reports: This plugin is built for Jenkins 1.538 or newer. It may or may not work in your Jenkins.*
          • I have a test instance of Jenkins which I can upgrade to 1.538 and I'll update Maven Project Plugin to 2.1.
          • Will re-run matrix job tests to see if the combined Jenkins/Matrix plugin upgrade proves successful.

          S Stack added a comment - @Oleg, thank you very much . We are running Jenkins 1.518 using Maven Project Plugin 1.511 . Regarding Maven 2.1 , update center reports: This plugin is built for Jenkins 1.538 or newer. It may or may not work in your Jenkins.* I have a test instance of Jenkins which I can upgrade to 1.538 and I'll update Maven Project Plugin to 2.1 . Will re-run matrix job tests to see if the combined Jenkins/Matrix plugin upgrade proves successful.

          S Stack added a comment - - edited

          @Oleg, I take it the "new Maven Wagon version" from your comment doesn't equate to the wagon-maven-plugin whose last released version appears to be 1.0-beta-4.

          • Can you explain more about a new Maven Wagon version please?

          I've upgraded a test server to Jenkins 1.538 and Maven Project plugin 2.1. However, in the topmost parent POM of our application, <wagon-maven-plugin.version> is set to 1.0-beta-4. The matrix job is still failing when run concurrently and succeeds when run sequentially. The failure symptom is always the same: wagon-maven-plugin:1.0-beta-4:upload appears to SCP the artifact (and we do see the zip file in the Jenkins workspace) but maven-antrun-plugin:1.7:run fails because it cannot find the artifact on the remote server.

          S Stack added a comment - - edited @Oleg, I take it the "new Maven Wagon version" from your comment doesn't equate to the wagon-maven-plugin whose last released version appears to be 1.0-beta-4 . Can you explain more about a new Maven Wagon version please? If you look at http://jira.codehaus.org/browse/WAGON#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel , the last wagon-maven-plugin release was 2.6 . But I can’t find a 2.x jar anywhere including Maven Central. I've upgraded a test server to Jenkins 1.538 and Maven Project plugin 2.1 . However, in the topmost parent POM of our application, <wagon-maven-plugin.version> is set to 1.0-beta-4 . The matrix job is still failing when run concurrently and succeeds when run sequentially. The failure symptom is always the same: wagon-maven-plugin:1.0-beta-4:upload appears to SCP the artifact (and we do see the zip file in the Jenkins workspace) but maven-antrun-plugin:1.7:run fails because it cannot find the artifact on the remote server.

          Oleg Nenashev added a comment -

          Sorry, I've forgot to reply to this issue several months ago.
          I'll try to investigate the issue on my installations

          Oleg Nenashev added a comment - Sorry, I've forgot to reply to this issue several months ago. I'll try to investigate the issue on my installations

            Unassigned Unassigned
            sstack S Stack
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: