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. This way they will be uploaded together with the artifacts and repo files.

Pipeline filesystem