Hello Jenkins Team, I still have not heard back regarding my query last week about the Maven Jenkins build options. Could someone take a look and respond?
Thank you for your time and consideration. David Alayachew On Wed, Sep 24, 2025, 12:48 PM David Alayachew <[email protected]> wrote: > Hello, > > I do not understand your question. What do you mean by Slack group? I do > not know of any Slack group, so if there is one, I cannot grant you access > to it. > > If you are asking about having the ability to join this google groups > discussion, it appears that you have already successfully done so. > > On Wed, Sep 24, 2025, 11:41 AM muni bhasker <[email protected]> > wrote: > >> Hi >> >> You have slack group so I cloud join. >> >> >> Thank you >> >> On Tue, 23 Sep 2025 at 7:05 PM, David Alayachew <[email protected]> >> wrote: >> >>> Hello Jenkins Team, >>> >>> I have a GitHub repo with a Maven project with over 50 sub-modules, all >>> in the same repo. All of those sub-modules are under a single aggregate pom >>> file. >>> >>> I created a single Maven job pointed to the aggregate pom, and on the >>> first run, all sub-modules were discovered as expected. >>> >>> Now, I want these jobs to build in parallel. So, I checked the checkbox >>> that says "Build modules in parallel". >>> >>> But when I looked at the nodes used, all of the builds occurred on a >>> single node, even though there are many other nodes available. And to be >>> clear, it was using all executors of that node, but still limiting itself >>> to a single node. >>> >>> So, that meant that, even though the queue had 40+ jobs queued up, once >>> all the executors on that single node were occupied, it didn't matter if >>> any of the other nodes were free, no work would be picked up by them. >>> >>> On a second attempt, a different node was used, but the same behaviour >>> -- all sub-modules only executed on this second node. >>> >>> Is this behaviour overridable? Or am I potentially doing things wrong? >>> Again, I am only using the Jenkins Maven Job, not a Jenkinsfile or anything >>> like that. >>> >>> And as a workaround, I could just make a new Maven Job for each Maven >>> sub-module. Doing it this way, now I do actually run on many free nodes. >>> >>> But that has the downside of increasing the maintenance burden >>> immensely. Remember, I have over 50 sub-modules. If I need to add new >>> functionality, that's 50 Jenkins jobs that I need to update. Not ideal at >>> all. >>> >>> Thank you for your time and help. >>> >>> -- >>> 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 visit >>> https://groups.google.com/d/msgid/jenkinsci-users/CAA9v-_M1Ex2E%2Bn2MGwH6RfT3ek0T23QX6VyQKcmRfbUhJ6N79w%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/CAA9v-_M1Ex2E%2Bn2MGwH6RfT3ek0T23QX6VyQKcmRfbUhJ6N79w%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> 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 visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAO54Onviqjzw__p6MnVw7yG6LF0khG7QONxbYRFRCYdYvh_Hfw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAO54Onviqjzw__p6MnVw7yG6LF0khG7QONxbYRFRCYdYvh_Hfw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 visit https://groups.google.com/d/msgid/jenkinsci-users/CAA9v-_Og%2B4tFhMa%3D88e06w8zPhr59sV7m7-m7SxTxrpNvwEDvg%40mail.gmail.com.
