-
Improvement
-
Resolution: Fixed
-
Minor
-
None
There are several steps which the 'withMaven' command executes, which people might want to skip.
The documentation states:
| Generated Artifact | Archiving and the fingerprinting of the artifacts and attached artifacts generated by the Maven build (jar, sources jar, javadocs jar...) | `.skip-archive-generated-artifacts` | |
| Generated JUnit and Surefire reports | Publishing of the JUnit / Surefire reports generated by the Maven build | JUnit Plugin | `.skip-publish-junit-results` |
| Generated Findbugs reports | Publishing of the Findbugs reports generated by the Maven build | FindBugs Plugin | `.skip-publish-findbugs-results` |
| Tasks scanner report | Publishing of a report of the "FIXME" and "TODO" tasks found in the java source code | Jenkins Tasks Scanner Plugin | `.skip-task-scanner` |
(1) Jenkins Plugin to publish the reports on the Jenkins build page. If the plugin is not installed, then the MAven report is ignored.
(2) Experimental feature.
Marker file to temporarily disable the feature for a specific Maven build.
Typically used to disable a reporter for a specific build that would generate too much data for the default configuration of the reporter (e.g. too many generated artifacts...) or to workaround a bug in the "withMaven" waiting for a fix. These marker file must be located in the home directory of the build.
Currently the only option to disable these steps is to use so-called marker files. It would be nicer if this could (also) be controlled by passing options to 'withMaven'.
E.g
withMaven(
options: [
skipArchiveGeneratedArtifacts: true
]
)
- is duplicated by
-
-
- Closed
-
