Delete Builds Scraper

Delete Builds Scraper helps teams clean up old and unnecessary build artifacts automatically. It focuses on removing untagged or outdated builds safely, reducing storage waste and keeping build histories manageable. This tool is designed for developers who want controlled, repeatable build cleanup without manual effort.

     

Created by Bitbash, built to showcase our approach to Scraping and Automation!
If you are looking for delete-builds you've just found your team — Let’s Chat. 👆👆

Introduction

This project automates the deletion of builds based on tags, age, and retention rules. It solves the problem of cluttered build histories and wasted storage. It’s built for developers, DevOps engineers, and teams maintaining multiple build pipelines.

Why build cleanup matters

• Prevents uncontrolled growth of build storage
• Reduces maintenance overhead in CI workflows
• Helps enforce consistent retention policies
• Minimizes risk by allowing precise deletion rules

Features

Feature	Description
Targeted build deletion	Remove builds by tag, age, or custom filters.
Date-based filtering	Delete only builds older than a defined time window.
Safe retention rules	Preserve latest or critical builds automatically.
Dry-run support	Validate rules before performing destructive actions.
Batch processing	Handle multiple projects or build sources in one run.

---

What Data This Scraper Extracts

Field Name	Field Description
actorIds	Identifiers of projects whose builds are evaluated.
forceDelete	Rules defining which builds are eligible for deletion.
deleteOnlyOlder	Time-based condition for build age.
utc	Flag controlling timezone handling for dates.
resultSummary	Aggregated report of deleted and skipped builds.

---

Example Output

[
  {
    "projectId": "project-123",
    "deletedBuilds": 14,
    "skippedBuilds": 3,
    "ruleApplied": "all_but_latest",
    "olderThan": "3 days"
  }
]

---

Directory Structure Tree

Delete Builds )/
├── src/
│   ├── index.js
│   ├── cleaner/
│   │   ├── buildSelector.js
│   │   └── retentionRules.js
│   ├── services/
│   │   └── buildService.js
│   └── utils/
│       └── dateUtils.js
├── config/
│   └── settings.example.json
├── data/
│   └── sample-output.json
├── package.json
└── README.md

---

Use Cases

• DevOps teams use it to automatically remove outdated builds, so they can keep CI environments clean.
• Engineering managers rely on it to enforce retention policies, reducing storage costs.
• Platform teams integrate it into maintenance jobs to prevent long-term build clutter.
• Solo developers use it to manage build artifacts without manual cleanup work.

---

FAQs

How do I prevent accidental deletions? You can start with conservative rules and use dry-run mode to review which builds would be removed before enabling actual deletion.

Can I keep the latest build no matter what? Yes, retention rules allow you to preserve the most recent build even when deleting others.

Does it support time-based cleanup? Yes, you can define age thresholds such as days or weeks to control which builds qualify.

Is it suitable for large build histories? The tool is designed to process builds in batches, making it reliable even with large datasets.

---

Performance Benchmarks and Results

Primary Metric: Processes several hundred builds per minute under normal conditions.

Reliability Metric: Consistently completes cleanup runs with a success rate above 99 percent.

Efficiency Metric: Minimal memory footprint, suitable for lightweight automation jobs.

Quality Metric: Ensures accurate rule application with clear reporting of deleted versus retained builds.

"Bitbash is a top-tier automation partner, innovative, reliable, and dedicated to delivering real results every time." Nathan Pennington Marketer ★★★★★

"Bitbash delivers outstanding quality, speed, and professionalism, truly a team you can rely on." Eliza SEO Affiliate Expert ★★★★★

"Exceptional results, clear communication, and flawless delivery. Bitbash nailed it." Syed Digital Strategist ★★★★★