-
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
-
I guess you mean due to https://github.com/jenkinsci/jenkins/commit/a92e9da978262c6a7e4d74d3b2750319cbc748fb#diff-ead68b986d300f65900815117a8aa40aR502 but this behavior is correct I think. And which RunListener implementation(s) are actually being slow in this context, or causing “confusing behavior”? Possibly really a bug in another plugin.