Repository navigation
Build and test PHP images together on native GitHub runners - #64
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build FPM/SSH images together on native GitHub runners and verify upstream PHP patch versions before publishing. Each run resolves one immutable PHP base index per version branch, verifies that AMD64 and ARM64 agree on the full patch version, and uses those same bases for testing and publishing.
Changes
build-versions.json. A preparation job verifies both upstream architectures, records their full PHP versions and immutable index digests in its summary, and supplies the build and manifest matrices.expected-versionsJSON map for manual release runs. Build only listed branches and reject unavailable/wrong patches, incomplete platform updates, unknown branches, and duplicate keys before building. PR runs resolve all configured branches; publishing runs are manual-only.Validation
Final GitHub Actions run: preparation plus all eight native version/architecture build/runtime jobs passed. All expensive compilation and installation steps were cache hits in every build (28–29 cached vertices per job). PR publishing steps were skipped.
Cold/warm cache benchmark: median Bake build/load/cache-export time dropped from 4m42s cold to 46s warm, approximately 6× faster. Runner setup and runtime tests are excluded from these timings.