Difference between build and deploy in Bamboo about expiration

Question

What's needed in the question is a comparison of the terms "build" and "deploy" on Bamboo, specifically how the two differ in their timeout or lifespan in the platform. The answer should describe how Bamboo deals with builds and deployments over time-that is, how long each artifact or outcome is available before being deleted or archived.

Answer 1

In Bamboo, "build" and "deploy" processes have different objectives as well as different handling of expiration.
Build Expiration:
Builds are created after compiling and testing changes in code. Even though Bamboo preserves the history of a build as part of records, older builds will consume unnecessary storage.
Build Expiration: Build expiration policies automatically eliminate older or less relevant builds. You can control how many builds Bamboo should keep or even time-based, for example, delete the builds older than 30 days.
Deploy Expiration:
This deployment or promotion of a build to several environments, including the staging and production, and the build will track the history of the deployment.
Expire deployment policies clean up older deployment records so versions cannot occupy space. Similar to builds, you can set up Bamboo to automatically delete old deployment histories after a certain number of days or by the number of versions kept.
Key Difference:
Build expiry addresses compiled code and test results, whereas deploy expiry focuses on the handling of versions and releases pushed toward various environments.




 

Answer 2

Because builds and deployments are separate entities in Atlassian Bamboo, their expiration policies vary in how they address cleanup and retention:

• The term "build" in Bamboo refers to the output of a continuous integration pipeline run, which generates artifacts or results according to the source code and defined jobs.
• Duration: Managed at the plan or worldwide level by the Build Retention Policy.
• It allows you to specify how long builds are stored (for example, keeping only the most recent "n" builds or builds that fall within a given time period).
• According to the guideline, older builds are automatically removed unless they are marked as favorites or specifically excluded from the cleanup.
• In Bamboo, the process of propagating artifacts from a build to other environments (such as staging or production) is known as deployment.
• Termination: Under the Deployment Version Retention Policy's control.
• Retention can be set up for deployment versions according to criteria like successful or unsuccessful deployments.
• Expiration policies enable fine-tuned control to maintain versions relevant to active environments and are unique to each deployment project.
• The main distinction in expiration is that build Expiration concentrates on clearing up logs and artifacts associated with CI builds.
• In deployment environments, deployment records and version histories are managed by deployment expiration.

Both are essential for preserving storage effectiveness and system performance while guaranteeing that important documents are always available.

Advance your career with a DevOps Master's Program—master CI/CD, automation, Kubernetes, and cloud technologies. Enroll now!