Incremental Multi-Module Maven Builds

[Jason Terk]

Hello,

We have a large, multi-module maven project that we're attempting to build incrementally, based on SCM changes. Using either Jenkins' built-in incremental-build option or scm-changes-updates-maven-extension we're able to limit the build to just those modules that changed, but the overall status of the job is "NOT_BUILT". How can we build incrementally and get Jenkins to recognize a build that only built a subset of the modules in the project as "successful"?

Thanks,
-Jason Terk

[Indra Gunawan (ingunawa)]

I am wondering are you using scm-changes-updates-maven-extension maven
plugin from https://github.com/nwiechmann/scm-changes-maven-extension?
Is it working with git or only meant for SVN?

Are you referring to Maven2/3 Job Type¹s option: "Incremental build - only
build changed modules² for "Jenkins' built-in incremental-build² ?

Thank you.
-Indra

On 11/5/15, 10:50 AM, "jenkins...@googlegroups.com"

>--
>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 jenkinsci-use...@googlegroups.com.
>To view this discussion on the web visit
>https://groups.google.com/d/msgid/jenkinsci-users/m2y4ecffgv.fsf%40evernot
>e.com.
>For more options, visit https://groups.google.com/d/optout.

[Jason Terk]

We tried using scm-changes-updates-maven-extension with a git repository; we had to change it slightly to work with maven 3.2.

We've also tried using the Job type option you mentioned.

In both cases unmodified modules are correctly skipped (and those dependencies are loaded from our internal maven repository) and the overall job status is "NOT_BUILT".

-Jason