Hello all, After giving a pretty thorough review of the code base, it's pretty clear that the assumption that the build occurs on a single node is assumed everywhere throughout the codebase. Updating the logic to work on multiple nodes would involve weaving through a lot of implicit assumptions, and would require me to make a lot of fairly intrusive changes in a bunch of places in the form of new parameters and value weaving.
Sadly, I've come to the same conclusion as the maintainers -- it's not worth the effort. Even if I did put in the effort, there's an extremely high chance I'd introduce a large number of bugs. It's just not wise to do. Maybe someone more intimately familiar than me can give it a shot, but considering that the maintainers themselves seem to be putting their efforts into the Jenkinsfile path, it's pretty clear that that is unlikely. For the maintainers, feel free to point back to this discussion thread in case anyone else makes the same feature request in the future. My maven jobs involve a lot of brittle, complex, and ugly logic, and yet, trying to get it done via the Jenkinsfile is honestly not that bad. Plus, since that logic is repeated in a lot of places, I can extract that into files, and use those to create simple, modular calls. I'll close the Jira ticket, and point back to this response as the close reason. Thanks again for the time and help everyone. David Alayachew On Thu, Oct 2, 2025 at 8:48 PM David Alayachew <[email protected]> wrote: > This goes to anyone else as well -- if anyone has any feedback or > criticisms, I would appreciate it. For both my created Feature Request, as > well as the soon-to-be-created PR. > > On Thu, Oct 2, 2025 at 8:35 PM David Alayachew <[email protected]> > wrote: > >> Thanks again for the help Mark. >> >> Here is my Feature Request -- >> https://issues.jenkins.io/browse/JENKINS-76168 >> >> I will now start working on the PR. >> >> I will read through this thoroughly, then reference it when building my >> PR -- https://github.com/jenkinsci/maven-plugin?tab=contributing-ov-file >> >> I understand that my PR is unlikely to be accepted. Nonetheless, if you >> have any suggestions on what to watch out for or things to improve my >> submission (to better my chances of getting it approved), I would >> appreciate it. At the end of the day, I think having this feature will >> improve the Maven plugin in a fundamental way. And since the feature >> request only simplifies what is already possible (creating multiple jobs >> manually), I think there is a decent chance that this might be seen >> favorably. >> >> Thanks yet again for the help thus far. >> >> >> On Wed, Oct 1, 2025 at 10:10 AM David Alayachew <[email protected]> >> wrote: >> >>> Thank you very much! >>> >>> I just scoured all the way to page 16 out of 20 (chronologically, so the >>> remaining tickets are <=2011), and the only one that even appeared relevant >>> was https://issues.jenkins.io/browse/JENKINS-11825?jql=Component%3D16033 >>> . >>> >>> I'll go ahead and start looking into making the change myself, submit >>> the pr, and then see if the incremental build is good enough to share. Best >>> case scenario, it is, and we can merge it in so that everyone who uses the >>> Maven Plugin will be able to benefit. >>> >>> I'll post my PR to this thread if/once I get it done. >>> >>> Thanks again for your time and help! >>> David Alayachew >>> >>> On Wed, Oct 1, 2025, 9:54 AM Mark Waite <[email protected]> >>> wrote: >>> >>>> On Wednesday, October 1, 2025 at 6:30:28 AM UTC-6 David wrote: >>>> >>>> And to be clear, I am more than happy to make the change myself and >>>> offer a complete pull request. >>>> >>>> >>>> If you're willing to do the work yourself, then you can immediately use >>>> the result of that work on your installation, whether or not it is ever >>>> included in a release of the Maven plugin. >>>> >>>> >>>> I am more so making sure that a request and offer like this would even >>>> be welcome to the team. It seems yes, but while I have you here, I figured >>>> I'd ask. >>>> >>>> >>>> The Maven integration plugin is not being actively enhanced. I doubt >>>> that your pull request will be merged, but even if it is not merged, you >>>> can use the incremental build of your pull request and allow others to have >>>> access to that incremental build as well. >>>> >>>> Mark Waite >>>> >>>> -- >>>> 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/2344e980-b5c9-4e5a-88b1-b255f56fcbdcn%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-users/2344e980-b5c9-4e5a-88b1-b255f56fcbdcn%40googlegroups.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-_Md8t1dPG%2Bb25%3D5Sa15ZMKzJEpqc%3DC%2BrtSN3OzsYvJFtQ%40mail.gmail.com.
