Hi, we're using a couple of slaves to build our many branches "on-push". There is no fix assignment between slave node and branch-building job, so it will happen regularly that a build job is run on a different node then the build job before.
Each job stores its Maven artifacts in a job-specific Maven repository - which is not only job-specific but unfortunately also slave-node-specific. Scenario: - Maven reactor build job *n *of branch *B *runs on slave *x*. Created artifacts are stored in the job-specific Maven repository for branch *B* on node *x*. - Maven reactor build job *n+1 *starts on slave node *y*. It determines which modules to build - and more importantly - which not, since those modules' artifacts have been built during job *n*. Unfortunately those built artifacts have been stored on node *x*. Node *y* may have artifacts older than build *n*, but those from build *n* are missing - Jenkins job does an inconsistent reactor build of mixed version modules. Question: Is there a possible solution other than having a fixed assignment between branch job and slave node? Thanks ind advance, Christian -- 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/935b8052-9805-4705-9b88-44a12a9c3721%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
