-
New Feature
-
Resolution: Unresolved
-
Minor
When using the plugin https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin with several conditionals it might be hard to debug and test all those cases, so it's worth splitting the logic and refactor a bit by using another approach
Severity: low
Further details under:
[JENKINS-42269] Cyclomatic complexity > 4 when using Conditional BuildStep Plugin
Description |
Original:
When the plugin knowledge database is installed is a good practise to force the analyser and therefore share build defects and detect them proactively and in case we don't want to use it then explain the reason in the job description by using the control comment Severity: Low |
New:
When using the plugin https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin with several conditionals it might be hard to debug and test all those cases, so it's worth splitting the logic and refactor a bit by using another approach Severity: low |
Labels | Original: 0.7.0 | New: 0.8.0 |
Description |
Original:
When using the plugin https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin with several conditionals it might be hard to debug and test all those cases, so it's worth splitting the logic and refactor a bit by using another approach Severity: low |
New:
When using the plugin https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin with several conditionals it might be hard to debug and test all those cases, so it's worth splitting the logic and refactor a bit by using another approach Severity: low Further details under: - https://www.cloudbees.com/sites/default/files/2016-jenkins-world-enforcing_jenkins_best_practices.pdf |
Labels | Original: 0.8.0 | New: 0.9.0 |
Labels | Original: 0.9.0 | New: 0.11.0 |