Appearance
Files
Use Library → Files to manage uploaded files and collected job output. Organize your files into folders. System groups files managed by packages, OS images and other resources.
Using files
Upload content and wait for malware scanning before using it. Reference the file from the task that needs it, such as Place file. Use Published Downloads when content should be downloadable without signing in.
Replace package installers, OS images and similar system-managed content through the owning resource's editor.
Publishing to a file
Use Publish to file in Collect runner artifacts to publish collected output as a new version of a selected file. Jobs referencing that file use its current version without needing their file selection updated. Each run keeps the version captured at its start, including for retries.
Publication happens during collection. Place collection after build and verification steps; a later job failure does not undo publication.
To select a destination before content exists, choose Actions → Create file reference. Upload or publish content before starting a job that uses it. AI agents can also create file references through configuration proposals.
See Build once, deploy independently for a complete example.
Versions and retention
Open Versions to download retained content or change its expiry. For user-managed files, you can also delete previous versions or use Restore content to make an earlier version current as a new version.
The file's expiry setting applies to future versions; change existing versions' expiry in Versions. Keep at least preserves a minimum number of the newest versions even after expiry. Manual deletion of previous versions bypasses this minimum.
The current version of a reusable file is protected from individual deletion and automatic expiry. Content required by an active resource or unfinished job also remains available. Inspect References to find its uses.
Standalone job output can expire even when it has only one version. See Artifact retention for collected output and sensitive files with fixed maximum lifetimes.
Revisions
Revisions records changes to file settings, such as its name, folder and retention policy. Restoring a revision restores those settings and leaves the current content unchanged.
See Configuration revisions and proposals for comparing, restoring and deleting configuration history.
Deleting files
Review References before deleting a file and update jobs or resources that still need it. Deleting a file deletes all its versions. An unfinished job or active resource using its content blocks deletion.
Deleting a package, OS image or similar owning resource also deletes its associated files. Endpoint attachments and standalone job outputs can be deleted directly from System → Endpoints and System → Job outputs.