-
Notifications
You must be signed in to change notification settings - Fork 45
Publish results
Sam Gleske edited this page Apr 11, 2018
·
11 revisions
Publishing the results of a build could be a number of different types of artifacts. The settings for collecting results are grouped under jenkins > collect in the YAML.
Currently, the existing supported results collected are:
-
artifacts- Binary artifacts. -
junit- Java unit test reports (or junit-compatible XML). -
cobertura- cobertura code coverage results.
There is a short and long format for publishing results. The following is example YAML of short format for publishing results.
jenkins:
collect:
artifacts: 'file file pattern'
junit: 'file pattern to JUnit XML'
cobertura: 'path to coverage.xml'Short form example:
jenkins:
collect:
artifacts: 'build/libs/*.jar'The short form assumes defaults from the long form YAML. The following is the long form example including defaults for each value when the short form is used.
jenkins:
collect:
artifacts:
path: 'build/libs/*.jar'
excludes: ''
allowEmptyArchive: false
caseSensitive: true
defaultExcludes: trueThe options are documented in the Jenkins source code in the following places.
-
artifacts
path. -
artifacts
excludes. -
artifacts
allowEmptyArchive. -
artifacts
caseSensitive. -
artifacts
defaultExcludes.
JUnit YAML only has a short form:
jenkins:
collect:Customize behavior using the long form. The following has defaults defined for the short form:
- Build overview
- Supported languages
- Supported build tools
- Publish results
- Additional topics:
- Quickstart
- Background information
- Knowledge checklist
- Required Jenkins Plugins
- Labels for Jenkins Agents
- Key security concepts
- Operationalize Jenkins
- High availability
- Disaster recovery
- Pipeline support
- Extending support