Learn how to minimize risks when having third-party dependencies.

Phaskell's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, Phaskell offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

Planet Haskell

Bazel builds often depend on external services that can fail due to outages, removed artifacts, rate limiting, or checksum drift. This post covers a layered set of strategies to improve build reliability: always use SHA-256 checksums, prefer GitHub releases over dynamic archives, use retry flags for unstable downloads, set up an internal repository manager (Artifactory, Nexus, etc.) with fallback URLs, configure Bazel's downloader to rewrite or block external fetches, use pull-through caches or the Remote Asset API, leverage Bazel sandboxing to enforce network isolation, and use the new --module_mirrors flag (Bazel 8.4+) and remote repository caches (Bazel 9). The post also highlights that genrule-level network calls bypass Bazel's downloader config entirely, requiring firewall-level controls or sandbox network blocking. Chaos testing in staging CI is recommended to validate resilience before real outages occur.

Accessing external resources reliably with Bazel