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

"No artifacts are recorded. Is this a Maven project?" only for parallel builds

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      I recently enable deployment to a repo post-build action. The deploying part
      works fine but whenever I activate parallel builds things go wrong. The top
      level --aka parent – pom.xml obviously has no artifact to deploy and so the
      build is marked as failed pretty quickly. That's a problem Disable parallel
      builds and it works!

      Note that despite the build being marked a failed Hudson still launches the
      parallel compilation of the modules

          [JENKINS-3788] "No artifacts are recorded. Is this a Maven project?" only for parallel builds

          dvrzalik added a comment -

          Wrong component...

          dvrzalik added a comment - Wrong component...

          Given that there's a work around, re-prioritizing.

          Kohsuke Kawaguchi added a comment - Given that there's a work around, re-prioritizing.

          jfreej added a comment -

          We are seeing the same "No artifacts are recorded. Is this a Maven project?" error when "Build modules in parallel" is enabled. Our main POM is an aggregator POM that has many modules.

          jfreej added a comment - We are seeing the same "No artifacts are recorded. Is this a Maven project?" error when "Build modules in parallel" is enabled. Our main POM is an aggregator POM that has many modules.

          We have the same problem.
          Since our build takes a little over an hour we would really benefit if we could build the modules in parallel.

          Also can anyone tell me what the help note means:

          'When your build uses "aggregator-style" multi-module aware mojos, you'd have to leave this option unchecked so that the mojo will have access to all of your modules.'

          Simon van der Sluis added a comment - We have the same problem. Since our build takes a little over an hour we would really benefit if we could build the modules in parallel. Also can anyone tell me what the help note means: 'When your build uses "aggregator-style" multi-module aware mojos, you'd have to leave this option unchecked so that the mojo will have access to all of your modules.'

          kutzi added a comment -

          AFAIK "Build modules in parallel" is considered deprecated now - though it's unfortunately not marked as such.

          If you want to build modules in parallel, I'd suggest Maven3's -T option. That one should work fine.

          kutzi added a comment - AFAIK "Build modules in parallel" is considered deprecated now - though it's unfortunately not marked as such. If you want to build modules in parallel, I'd suggest Maven3's -T option. That one should work fine.

            Unassigned Unassigned
            jparent jparent
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: