Build artifacts are the code files and outputs, including file contents and metadata, from a software build process, and are often stored in a cloud storage service. Artifacts can be downloaded from storage and used in subsequent testing or deploy steps in your software development pipeline.
Access an artifact
Use the Artifacts list features to access information and functions related to artifacts generated by workflow runs.
| Your artifact may not yet be listed in Artifacts because it is still waiting to be generated. |
To access artifacts:
-
Navigate to details for a component.
-
Select the Artifacts tab. Artifacts built or deployed by workflow runs are displayed.
Figure 1. Artifacts
-
Manage artifacts.
-
Navigate to applicable data and features using the breadcrumb menus and links.
-
Access the GIT repository linked to component by selecting the repository name link.
-
Filter list by Artifact name.
-
Locate a specific artifact using the Search feature.
-
Show or hide artifact version by selecting Display full version history.
-
Add a new artifact version by selecting Create version.
-
Review the Name, Version, Digest, Location Published by, Date created, and Deployment history information.
-
-
Use these features to:
-
Copy the path to a specific artifact or artifact digest by selecting
. -
Access the run details for the workflow that built the artifact by selecting the workflow run name in the Published by column.
-
Review the deployment history of a specific artifact by selecting
in the Deployment history column.
-
Create an artifact version
Use this feature to configure a new artifact version.
To create an artifact version:
-
Navigate to details for a component.
-
Select the Artifacts tab. Artifacts built or deployed by workflow runs are displayed.
-
Select Create version. The Create version screen displays.
View image
Figure 2. Create version -
Complete the required and applicable Create version fields.
View fields
name: The name of the artifact to send to the CloudBees platform for artifact traceability purposes.version: The version of the artifact to send to the CloudBees platform for artifact traceability purposes.url: The URL where the artifact version is located. For example, docker.io/myapp/myimg:1.0.0.digest: The artifact digest that uniquely identifies the artifact. -
Select Save.
View artifact deployment history
Use the Deployment history features to access information and functions related to a deployed artifact.
| To collect artifact deployment data, a workflow must contain the Register an artifact deployed to an environment action. |
To access deployed artifact features:
-
Navigate to details for a component.
-
Select the Artifacts tab. Artifacts built or deployed by workflow runs are displayed.
-
Select
in the Deployment history column. The Deployment history for the artifact displays.
Figure 3. Deployment history
-
Manage deployment history list.
-
Filter deployments by Name.
-
Locate a specific deployment run using the Search feature.
-
-
Review the Deployment run, Status, Digest, Environment name, and Deployment date information.
-
Use these features to:
-
Copy the path to a specific artifact or artifact digest by selecting
. -
Access the run details for the workflow that deployed the artifact by selecting the workflow run name in the Deployment run column.
-