Skip to content
BoringCache

Artifacts

Build outputs for testing,
deployment, and releases.

Keep binaries, test reports, and release packages beyond a single job. Pass exact outputs between pipelines, deploy them later, or publish a release on your own domain.

Set up Artifacts View plans
Release artifacts

Release v1.2.0

One immutable artifact

  • app-linux.tar.gz
  • test-results.xml
  • checksums.txt

Test

Deploy

Download

Use the same output from build to release.

An immutable Artifact ID identifies the files to download. Test and deploy that output without rebuilding it in the next job.

Across jobs

Pass the Artifact ID to the next stage.

Across CI systems

Upload or download with the CLI wherever the pipeline runs.

Outside CI

Retrieve a release package from a developer machine or deployment script.

Resume interrupted uploads.

Transfer files and directories directly to storage. Rerun the same upload command without sending completed parts again.

Retention for reports and releases.

Choose an expiry for temporary files. Administrators can keep release archives without automatic expiry. Artifact retention is separate from cache cleanup.

Choose retention →
Test reports
7 days
Release candidates
30 days
Release archives
No automatic expiry

Publish release downloads on your domain.

Give public release files immutable, versioned addresses using a managed download domain or a domain you own.

Configure release downloads

downloads.example.com
/releases/v1.2.0/app-linux.tar.gz

Custom domain Immutable file Public download

Keep signatures and provenance with your releases.

Upload your signatures, SBOMs, and provenance alongside a release. Verify those files with your signing tools.

Signed publication receipts

BoringCache signs a record of the files it accepts. The CLI checks that receipt and the downloaded file hashes.

Explore artifact verification →
release.tar.gz
Build output
bundle.sigstore.json
Cosign signature bundle
provenance.intoto.jsonl
Build provenance
sbom.spdx.json
Software bill of materials

Use included storage or connect your own.

Where build data is stored

Managed storage

Every plan

Cache · Artifacts · Registry

Included for Cache, Artifacts, and Registry on every plan. Start without setting up a storage account, with no BoringCache egress fees.

See plans and allowances →

Your own storage

Custom plan

Cache · Artifacts · Registry

S3 Azure Blob

Connect S3-compatible storage for Cache, Artifacts and Registry on Custom. Cache and Artifacts also support Azure Blob Storage. Your provider bills storage and transfers.

Explore BYOC →

Artifact upload and download.

The CLI uploads files or directories and downloads them by Artifact ID.

boringcache artifact push dist/ --name release
boringcache artifact pull "$ARTIFACT_ID" ./release
Set up Artifacts Compare plans