Overview

File artifacts are used to capture single files produced as part of a build. Example files include binaries and libraries produced as part of the build. You may also capture logs, reports, and other files of interest. Captured files may have post-processors applied to them to extract interesting features such as errors and warnings.

Configuration

name

A descriptive name, used within the web interface to identify the artifact. This name must be unique within the project.

This field is required.

file

The path of the file to capture, relative to the base directory for the build.

This field is required. This attribute supports Apache Ant style patterns, useful if you file you are specifying contains a version string or datestamp.

mime type

The MIME type of the file. This type will be passed to the web browser when the file is downloaded.

This field is not required. By default, the type will be guessed from the file name and content.

post-processors

Specifies the post-processors to apply to the file when it is captured. The available post-processors are described on the Project Post-Processors page.