Pipeline filesystem

Every pipeline has its own filesystem attached. The filesystem contains a clone of your repository in the revision selected in the latest run, together with the artifacts generated by your pipeline actions. It serves as the primary cache for your pipeline; this way, you don't need to fetch the whole repository and dependencies on every execution.

Artifacts

All files created during the execution will land in the filesystem marked with a diamond icon. You can browse and download them via the UI or with cURL (using a dedicated URL).

Configuration and static files

Not all files should be stored in the repository. For example, configuration files for a specific environment (dev/stage/production), or those that contain sensitive data. You can, however, upload them manually to the filesystem. These files are marked with blue icons and will be uploaded together with the artifacts and repo files.

Warning
Static files are preserved even when clearing the pipeline cache. They can only be removed manually from the filesystem.

Image loading...Pipeline filesystem

Image loading...Pipeline filesystem file types: repository, artifacts, static files

Managing files

Use the Add file button to:

  • Create a new file - Create a new file where you write code/content and assign it a name
  • Upload files - Upload files from your computer to the filesystem
  • Create a new directory - Create a new folder to organize files

Downloading filesystem

To download the entire filesystem (including all artifacts, static files, and repository content), click the three dots menu next to the Add file button and select Download. This will create a compressed archive containing all files in the pipeline filesystem.

Last modified on Oct 9, 2025