Forgot to mentioned that the build is happens on a slave node with Centos 6.6.
On Tuesday, 16 June 2015 10:05:54 UTC+8, Khar Yeow phang wrote: > > I've maven project that contain multiple modules, the structure is > illustrated as below, > Project-a-aggregation\pom.xml > --\ > module-a\pom.xml > module-b\pom.xml > module-b\pom.xml > module-e\pom.xml > --\ > parent\pom.xml > --\ > depmgmt\pom.xml > > > We build with maven-3.3.1 and with *clean install -T 4* in Jenkins ver. > 1.596.2 <http://jenkins-ci.org/> and Maven Integration plugin > <http://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin> 2.10 > We use workspace as local repository. > We check out fresh source code from svn every time. > We use maven-version plugin to update pom version in very build. E.g. > 1.1.0.123 > > It's very frustrated that where some time the aggregation/pom.xml, > depmgmt/pom.xml or prent/pom.xml are missing in the Artifactory deployment. > From the jenkins console log, we didn't see the log "[INFO] Deploying > artifact: " appear for one of these pom.xml. We have try clearing the > workspace, some time after clear the workspace it work but subsequence > build the symptom is back. > > Your ideal and contribution are very much appreciated. > > > Regards, > phang > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/36892235-89c3-434a-9bc4-f522077e197c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
