Overview
Artifacts are files and directories that are captured when commands are executed. Common examples of artifacts include command output (standard out and error), binary files (executables, libraries, JAR files) and reports (unit test reports, test coverage reports). For both custom and versioned projects, these artifacts are captured by using directives in the pulse file. For built-in projects, however, you can configure what artifacts are captured from the project's "configuration" tab.
In addition to capturing artifacts, you may also apply post-processing to them. Post-processing is used to extract features such as errors and warnings, as well as capture the output of test results.
Types of Artifacts
Pulse supports three types of artifact:
| Type |
Description |
| Directory |
A collection of files nested underneath a directory, e.g. a directory of test reports. |
| File |
A single file, e.g. a binary produced by the build. |
| Output |
Output (standard output and error) from the build command. This artifact is always present. |
Default Artifacts
Some project types are configured with artifacts by default. All projects always have a special artifact named "command output" that captures the output of the build command. This artifact may have post-processing applied as with all artifacts (see Project Output Processors). Additionally, maven and maven 2 are each configured with default artifacts that capture JUnit test reports from standard locations. You may modify these default artifacts to suit your project if necessary.
Managing Artifacts
To add a new artifact to your project, click the "add new artifact" link at the bottom of the "artifacts" table. This will take you to the Artifact Wizard, which will guide you through the process of adding the new artifact.
The configuration of existing artifacts may be edited by clicking the "edit" link in the corresponding row of the "artifacts" table. If you wish to delete an artifact, use the "delete" link in the corresponding row of the "artifacts" table.
