[
https://issues.jenkins-ci.org/browse/JENKINS-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158754#comment-158754
]
Simon van der Sluis commented on JENKINS-3788:
----------------------------------------------
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.'
> "No artifacts are recorded. Is this a Maven project?" only for parallel builds
> ------------------------------------------------------------------------------
>
> Key: JENKINS-3788
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3788
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: jparent
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
