Download & verify artifacts
A FORGE artifact is the durable packaged result of a build. Download and inspect it before treating the build as complete for your own workflow.Find the artifact
Open the completed build and review its artifact list. A build can produce more than one artifact depending on the workflow. Useful artifact metadata includes:- artifact ID
- name
- build/project owner
- created time
- file count
- total size
- checksum when available
- retention or expiration state
Download
Use the supported Starfire download action or Developer Platform artifact resource. Do not depend on temporary internal storage URLs or workspace paths.Verify checksum
When a checksum is exposed, calculate the checksum of the downloaded file with a compatible algorithm and compare the values. A matching checksum confirms that the downloaded bytes match the packaged artifact Starfire recorded. It does not prove the source code is secure or functionally correct.Inspect contents
Before deploying a generated software artifact:- review the file tree
- review dependency changes
- inspect environment/config examples
- confirm no secrets were embedded
- check validation results
- run project-specific tests in the target environment
Retention
Artifact retention can depend on plan, organization policy, artifact type, or administrator configuration. If the output matters long-term, store it in your normal source-control or release system rather than assuming Starfire is permanent archival storage.Expired artifacts
An expired artifact may no longer be downloadable even though historical build metadata remains. Rebuild from a known source state if you need a fresh artifact and no retained copy exists.Artifacts
Review the full artifact ownership and retention model.