website logo
Sign Up PricingApp Templates
⌘K
🚀Getting started
Create an account in Microtica
Create an application from template
Import an existing application
Scaling Applications in Microtica
Assign a Custom Domain
⏰Changelog
📚Ready-to-use Templates
Strapi Serverless
Medusa Server
Appwrite
SPA on CloudFront
Amazon EKS
Node.js
n8n Workflow Automation
Next.js
🤖Migrate to Microtica
Migrate from Heroku to AWS
🚦Pipelines
Pipeline Syntax
Steps
Stages
Artifacts
Variables
🔗Integrations
Connect an AWS account
Connect an Existing Kubernetes Cluster
Connect a Container Registry
⚙️Project Settings
Manage teammates
Manage pricing plan and billing
Docs powered by archbee 
12min

Artifacts

Artifacts persist data after the step is completed and may be used as a storage for deployment packages.

Microtica supports three types of artifacts:

  • File Artifacts
  • JSON Artifacts
  • Container Artifacts

File Artifacts

File artifacts are the most common type of artifacts used to produce a deployable package that consists of plain files organized in a folder structure.

microtica.yaml
|


Below is an example of a pipeline step that installs node modules and compiles the source code. Once the commands are executed, a new dst/ folder will be created that contains the compiled code with the modules, and we want to package only that folder.

microtica.yaml
|


In this case, we’ve defined one artifact named as primary (the name is just a way to recognize multiple artifacts). The artifact will contain all the files and folders inside the local dst/ path.

Packaging content

When you want to package a whole folder recursively, make sure that you end the path with a slash (/) so Microtica can distinguish single file from whole folder packaging.

To define an artifact that contains only one specific file just provide the path to the file:

microtica.yaml
|


You can also select multiple files by using standard Unix filename wildcard syntax:

microtica.yaml
|


The above example will produce an artifact containing all files with .js extension within dst folder.

To define secondary artifacts, just specify them under files.

microtica.yaml
|


Microtica will automatically package, store and manage File Artifacts on encrypted, durable blob storage in the cloud.

JSON Artifacts

Microtica allows you to define structured artifacts in JSON format that you can easily reference from other steps.

Basically, you define the path to the JSON file saved locally during the step execution. Then, the JSON object will become available to reference from other steps using a common JS syntax.

microtica.yaml
|


To demonstrate this, we can define a pipeline that first provisions a complete infrastructure in the cloud to host our SPA website and then deploy the source code on S3.

microtica.yaml
|


In the DeployInfra step, Terraform will generate a terraform.output file. This is a JSON file containing the outputs of the provisioned infrastructure.

The DeployWebsite step then references the outputs from the previous step by simply using ${DeployInfra.artifactsBucket} syntax. artifactsBucket is a property from terraform.output file.

Microtica will automatically store and manage JSON Artifacts on encrypted, durable blob storage in the cloud.

Container Artifacts

Microtica provides built-in support to build/push Container images on your preferred Docker registry.

To start working with Container artifacts you would first need to connect your Container registry from Microtica Portal. To connect new registy go to Project Integrations -> Container Registries.

Container Artifacts in Microtica
Container Artifacts in Microtica


The name provided when connecting a new registry will be used in the pipeline yaml to specify the artifacts destination.

microtica.yaml
|


After BuildAndPushDocker step is completed, image with name my_app_image and tag v0.1.0 will be pushed to dockerhub Docker registry connected within Microtica.

Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Variables
Docs powered by archbee 
TABLE OF CONTENTS
File Artifacts
JSON Artifacts
Container Artifacts