Publishing artifacts
When executing a job on an agent there are often artifacts created that we need to keep around. For example, JUnit creates xml reports that Go is able to parse in order to help you understand why the build is broken. Or you might create a flash video of your UI tests that we want displayed in Go.
To publish artifacts you add a an <artifact> tag to the job configuration. More information can be found on the Managing artifacts and reports page.
Example usages
Uploading JUnit xml reports
We are going to assume that the JUnit test reports are being placed in the "target/reports" folder.
- Click on the Administration tab
- Click on your pipeline
- For each job that runs JUnit:
- Click "Edit this job"
- Ensure the following "artifacts" block is in the job configuration
- Click "Save"
Uploading a flash video and displaying it as a sub-tab
We are going to assume that the flash file, and the html file referencing it, are being created in the "target/reports/recording" folder.
- Click on the Adminstration tab
- Click on your pipeline
- For each job that creates a flash video
- Click "Edit this job"
- Ensure the following "artifact" line is in the job configuration. This will copy all files from the "target/reports/recording" folder on the agent to the "recording" folder on Go server
- Ensure the following "tab" line is in the job configuration. This will create a tab called "Recording" that shows the html page found at "recording/recording/twist-recording.html" on Go server.
- Click "Save"
- Watch the flash video as a sub-tab on the Job Details page
