Page History

What are Artifacts?

Artifacts are files that were involved in the build process that are then registered in Continua CI as important files. By registering a file as an artifact, it can then be viewed through the browser or downloaded to the current user's computer. Artifacts are declared at the end of each stage by specifying artifact rules.

For a file to be an artifact, it must be located in the server's workspace. Files are declared as artifacts on each stage after the agent has finished syncing files with the server. This means that files that should become artifacts must be in the server's workspace both at the end of the stand and once the build has finished. All artifacts are relative to the server's workspace which means files in other locations cannot be added as artifacts.

Artifacts can only be viewed or downloaded if a user has the View/Download Artifacts permission.

Viewing Artifacts

Files that are registered as artifacts can be viewed on a specific build by navigating to the artifacts tab. On this page you will find every artifact that is linked to the current build.

Image Added

On this page you can access and view individual artifacts. There are three ways an artifact can be viewed:

• Download: This will download the artifact from the server onto the clients machine.
• Raw: This will open a new tab and the browser will attempt to open the file. The artifact and the artifact's file type are both sent to the browser and it is up to the browser how the file will be generated (Note that different browsers render file types differently). This means that this method should only be used on files that can be viewed through the browser.
• Special Views: File types can be associated with special views. See the next section for more information on these views.

Special Artifact Views

Artifacts can be associated an artifact type when specifying artifact rules. If an artifact is associated to one of these types, they can be opened in a special view within the Continua artifacts page. Check out the Artifact Rules page for more information on how to assign a view type to artifacts.

Continua currently supports the following special views.

Image

The Image special view is designed for any image files, i.e. .png, .bmp, .gif, .jpeg, etc. By setting an artifact to the image type you can then view those images straight from the artifacts page. 

A file can be typed as an image by adding the image type to the artifact rule. For example, if I want all .pngs in my output folder to be image artifacts, I would use the following artifact rule: image | output\*.png

The image view is shown below.

Image Added

NUnit

The NUnit special view is designed for .xml output files that are generated by NUnit. This special view generates a custom view based on the NUnit results. This view is shown below.

A file can be typed as NUnit by adding the NUnit type to the artifact rule. For example, if I want my tests.xml to be a NUnit artifact and this xml is in the output directory of the server's workspace, I would use the following artifact rule:  nunit | output\tests.xml

Image Added

Variable

The variable special view is mainly used for artifacts that are automatically generated for every build. These artfacts are:

• <agent_name>_Environment.xml: These files list all environment variables that are located on a specific agent. This file is generated while a stage is executing on a particular agent.  If a build has multiple stages and these stages are  run on multiple agents then you will get multiple <agent_name>_Environment.xml files.
• VariableNamespaces.xml: This artifact lists every Continua variable including the variables value at the end of the build. This file will list global, project, configuration and build variables.

How do I Create Artifacts?

Help, My Artifacts Can't be Found!

The artifacts tab on the build page shows a list of artifacts for the build. Each artifact listed displays a File Name, a File Size, a Created date, a MD5 hash of the file and a Relative Path. The relative path is relative to the workspace directory of the build.

...