Andre Lustosa

ANDRE LUSTOSA / TAG

#build-systems

3 entries with this tag.

  1. Build Pipelines Should Explain Their Decisions

    A pipeline becomes more useful when each stage records the evidence behind release, rejection, and later maintenance decisions.

  2. Hermetic Builds Begin at the Acquisition Boundary

    A build becomes explainable when every network-dependent input is acquired explicitly, recorded, and separated from the steps that construct the artifact.

  3. Testing the Package Beyond the Source Tree

    Several upstream fixes point to one packaging rule: exercise built artifacts, disabled paths, and dependency boundaries directly.

← All writing