Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: configurationslicing-plugin
-
Labels:
-
Environment:Debian 7.0 amd64 , Oracle JRE 7.0u17 x64 , Tomcat 7.0.40 , Jenkins 1.509.1 , de_DE.UTF-8
-
Similar Issues:
Description
From 1.36 to 1.37 something changed so we now see all modules of all our maven projects as separately configurable in configuration slicing.
Due to the number of projects and the huge number of modules within each of them, configuration slicing lost much of its usability.
Maybe the noted change "add support for folders" brought this change.
Would be nice to have a global config switch to set configuration slicing to default to the old behaviour no longer showing every single maven module in config slicing lists when not explicitely chosen to do so.
Reverting to 1.36 from 1.37 brought back the old behaviour for us so we can see again our projects without every single maven module listed besides them.
Attachments
Issue Links
- is related to
-
JENKINS-18554 NPE in Maven Version slicer in 1.37
-
- Resolved
-
Fairly obvious left overs from https://github.com/jenkinsci/configurationslicing-plugin/commit/cfcd3d0f6aec34035e773d656d1991aa45a8061c – The fix in https://github.com/jenkinsci/configurationslicing-plugin/commit/eefdd378edd33db54ec7e2abcddbc63ca7428fec only took care of Maven Version.