-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maven Multi Module Builds #60
Comments
@jan-molak, Can I take a run at this one? I'll take a look at the un-merged code for #62 (matrix builds) for inspriation but it will take a few months for me. |
@drekbour - of course you can! Thanks for offering your help 😄 |
Initial thoughts - there are several usecases here so I will implement multiple implementations of support "Display Maven modules" : [Hide|InPlace|Expanded] Hide InPlace
Expanded Not in scopePer project <jenkins.build.monitor.mode>InPlace</jenkins.build.monitor.mode> The existence of this property would supercede the above UI settings
|
Would your solution be able to handle several of the modules being built at the same? We are using the Jenkins threading options to help to keep the build times down. Setting our Jenkins build "Goals and options" for our parent pom to "-T2 clean deploy --fail-at-end". Just to let you know currently our multi maven parent pom has about 42 modules (we have never really tried going above -T4), and takes a long time. Also our Jenkins builds and monitors are on large screens near our desks and are already limited on space. If the main build had some kind of indicator on the current module being built embedded would suit our use case. |
"Expand" appears to work just fine with threading and FAE. |
@jan-molak For InPlace mode described here, I want to add a "subtitle" to the job which, in this case - shows the active Maven module during a build and the failed module when appropriate. Browsing though the many other issues and PRs I see people wanting similar "compound jobs" for other Jenkins features: dynamic (sub) title, nested lozenges or lozenges somehow structured together. What is your opinion? I think it's time you decided on how to support higher-order builds (Maven modules, Matrix, Multi-job, pipeline etc) as the implementations of each of these are going to conflict terribly with each other. |
@drekbour - yeah, I can certainly see the need for "higher-order jobs". I'm not sure what the answer should be though yet.. Let me think out loud for a moment :-) It seems to me that the problem is worth splitting into two smaller ones:
So far it looks like each type of a higher-order job could require a different visualisation:
It also looks to me that we might need to categorise each job depending on its traits*.
to start with, and perhaps:
and others, should people need them later? A What do you think? * Or perhaps tag it instead? With, say: "MultiModule, Claimed, ShowingCulprits", or something similar? Categorising feels simpler to start with though |
It's a complicated space. I'll add some more.
The rabbit hole goes deep So I wouldn't get hung up on implementation at all. It's right to think what is the job and how should it be (meaningfully) shown on a dashboard. What is reasonable to support and what not? I didn't (and still haven't) tried to think much further on this apart from liking choice, liking the subtitle mode in theory and realising we can have POM property control the board's choices here. |
We have a large multi module build using the maven reactor and would really like to be able to see the modules broken down into seperate status bars.
Is possible to track which sub-module is being built as its own status bar from the parent, this would especially be helping in a multi module build as we use threading argmuments to build them. It will also allow use to see the final status of each module as we use "--fail-at-end". Potentially when we do a release, using the mavne-release-plugin we can also see the release status of each artifact.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2116782-maven-multi-module-builds?utm_campaign=plugin&utm_content=tracker%2F580790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F580790&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: