Promote Build Artifacts Across Environments Using Bamboo Deployment Projects
Control artifact promotion from build to production with Bamboo Deployment Projects, manual approval gates, and audit history.
Loading…
ReadMeFeed / Community knowledge
#artifacts
Real questions. Useful conversations. Find the people who know your stack.
bambooGitHub Actions Artifacts Quietly Eat Your Storage Budget: How Retention Actually Works
GitHub Actions artifacts default to 90-day retention, which quietly inflates storage for noisy pipelines. How per-artifact retention-days, org caps, and API-based cleanup actually work.
githubControlling GitLab CI Artifact Expiration to Stop Storage Bloat
GitLab CI artifacts are kept forever unless you set artifacts: expire_in. Learn how to configure per-job retention, avoid common mistakes, and verify cleanup actually happens.
Controlling GitLab CI Artifact Retention with expire_in
Learn how to control GitLab CI artifact retention with the artifacts: expire_in keyword, see a concrete .gitlab-ci.yml example, and verify expiration via the UI and API.
GitHub Actions artifact retention limit exceeding 90-day maximum cap
The actions/upload-artifact action utilizes the retention-days input to manage the lifecycle of generated files. While the default is set to 7 days, the platform enforces a hard upper limit of 90 days for any workflow-level artifact storage. This constraint presents a challenge for long-term release tracking or compliance requirements where build outputs mus
githubactionsStale artifacts after interrupted Hardhat compilation
Goal Determine whether Hardhat guarantees mutual consistency between the artifacts/ compilation outputs and cache/ incremental-build metadata after a failed compile, process interruption, or concurrent invocation. Hardhat writes ABI and bytecode artifacts to artifacts/ and records source and import-graph content hashes in cache/. On a failed compile, the fai
hardhatHardhat reuses cached contract artifacts without checking Solidity source timestamps
Hardhat writes compiled contract artifacts to .cache/artifacts and reuses them on subsequent runs. The compiler does not appear to compare Solidity source modification times against cached artifact timestamps by default, so editing a contract file may leave stale ABI or bytecode in place. The --force flag bypasses the cache, but using it on every compile rem
solidityArtifact expiration policy silently deletes downstream artifacts after pipeline completion
Goal Maintain artifacts for downstream pipelines while respecting the configured expiration period. Constraints & Uncertainty GitLab allows expiration to be set globally, per-pipeline, or per-job. It is unclear whether artifacts referenced by downstream jobs are exempt from the same expiration rules or if they inherit the same policy as the originating j