Artifacts

Create and manage artifacts to ensure that the version of a pipeline that you are releasing to production is the same version that you have tested in your development and test environments.

An artifact is an immutable collection of resources (e.g. pipelines and script files) that is built as a compilation of executable assets and deployed to the specified environment when you publish. An artifact is built from a specific commit within the source code in your Git repository. Once published, the artifact is independent from the source code and is the version of a pipeline that is run by a schedule. Artifacts allow data team leaders to manage releases of published versions of their pipelines.

Video example

Expand this box to watch our video about Artifacts.

Video

Create an artifact

To make your pipelines available for scheduling, create an artifact by making commits, pushing your changes, and publishing.

Click the branch menu on the project bar.
Click Push local changes in the drop-down menu. The number displayed next to this option shows the number of committed changes that haven't been pushed yet. The Push local changes panel will open, displaying the list of local commits that you can push to remote.
Check the Publish checkbox and complete the required fields.
Click Push & Publish to save all your local commits to the remote repository and create an artifact. Otherwise, click Cancel to cancel your push and publish operation.

After pushing your changes and publishing your pipelines, you can then create a schedule to run either the latest version of a pipeline, or a specific version of a pipeline. View and deploy artifacts to other environments in the Artifacts tab on the Projects page.

Note

The version name that you choose when publishing must be unique, because it will be used to identify the artifact that will be built and deployed to the specified environment.

We recommend using a semantic versioning naming scheme that uses a combination of major and minor version numbers to track subsequent versions. For example, 0.1, 0.2, 1.0, 1.1, 2.0, and so on.

View artifacts

After publishing your pipelines based on the latest pushed code in your Git repository, you can view the artifacts that have been published in your project.

From the Your projects menu, select your project.
Navigate to the Artifacts tab.
Select the environment you want to view.

The following information is shown for each artifact:

Property	Description
Name	The name you entered in the Version name field when you pushed and published changes to a specific environment.
Deployed on	Timestamp that shows when the artifact was deployed to the selected environment.

Deploy an artifact to a different environment

After validating and testing in your development or test environment, you can then deploy the same artifact to a different environment. You must have Admin access to the environment you wish to deploy the artifact to.

From the Your projects menu, select your project.
Navigate to the Artifacts tab.
Select the environment that contains the artifact you want to deploy.
Click the more button ... on the corresponding row of the artifact.
Click Deploy to environment.
In the Deploy to environment dialog, select the environment you want to deploy the artifact to.
Click Deploy.