-
Bug
-
Resolution: Not A Defect
-
Major
-
None
This is due to the fact, that now all build listeners are called after every module as well. This might also break plugins.
Also, this leads to confusing behaviour when using incremental builds.
In our case, we have a huge project (~100 modules). An incremental build, which should only build about 5 modules waits for about 2 minutes (while moving through the listeners for all NOT_BUILT modules), before actually starting to work.
This was introduced by the fix for JENKINS-18846.
- is related to
-
JENKINS-18846 New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
-
- Resolved
-
[JENKINS-21597] New Maven Plugin causes slowdown for huge multimodule projects
Description |
Original:
Also, this causes an extreme slow down, especially when using incremental build. In our case, we have a huge project (~100 modules). An incremental build, which should only build about 5 modules waits for about 2 minutes (while moving through the listeners for all NOT_BUILT modules), before actually starting to work. This was introduced by the fix for [ |
New:
This is due to the fact, that now all build listeners are called after every module as well. This might also break plugins. Also, this leads to confusing behaviour when using incremental builds. In our case, we have a huge project (~100 modules). An incremental build, which should only build about 5 modules waits for about 2 minutes (while moving through the listeners for all NOT_BUILT modules), before actually starting to work. This was introduced by the fix for [ |
Summary | Original: New Maven Plugin causes build listeners to be called after the completion of every module, causing a lot of plugins to break | New: New Maven Plugin causes slowdown for huge multimodule projects |
Link |
New:
This issue is related to |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 153595 ] | New: JNJira + In-Review [ 194606 ] |