-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 2.97, pipeline-maven-plugin 3.2.0 alpha-2
-
-
pipeline-maven-3.11.0
When using logger org.jenkinsci.plugins.pipeline.maven with log level ALL, jgiven related output is not clear if the log entry is related to the plugin is not installed or if there is no jgiven report available on the project being built.
... [withMaven] Maven Publishers with default configuration: [org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher[disabled=false, scopes=[compile, provided, runtime], versions={snapshot:true, release:false}], ..., org.jenkinsci.plugins.pipeline.maven.publishers.JGivenTestsPublisher[disabled=false], ... [withMaven] Use default defined publisher for 'JGiven Publisher' ... [withMaven] Run 'JGiven Publisher'... [withMaven] jgivenPublisher - JGiven not found within your project dependencies, aborting. ...
No jgiven related information is seen on logger console (Manage Jenkins >> System Log >> "Your Maven Logger" >> Log Records)
Tested with petclinic project.
def dockerImage = 'maven' currentBuild.displayName = "#${currentBuild.number} ${dockerImage}" node('docker') { deleteDir() stage('build') { myimage = docker.image("${dockerImage}") myimage.inside() { checkout scm withMaven(){ sh "mvn clean package" } } } }
Tip:
Open Task Scanner publisher informs that the plugin is not installed.
... [withMaven] Run 'Open Task Scanner Publisher'... [withMaven] Jenkins Task Scanner Plugin not found, don't display results of source code scanning for 'TODO' and 'FIXME' in pipeline screen. ...
- links to
