Repository navigation
Keep packaging checks and the 32-layer budget aligned - #343
Merged
Merged
Conversation
chen21019
changed the title
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.
Align the performance source check with the existing canonical script COPY after
PR342 added the temporary Engine verifier to that same instruction.
The check still requires all canonical scripts, the exact destination and
permissions. No application code, configuration or performance default changes.
Also account for the base image's one layer in the existing 32-layer build budget.
A native probe confirms that even no-op RUN instructions consume a layer. Reuse
the tar already copied under
/tmp/pasturestack-runtime-security, verify itsexisting checksum, then install it in the same RUN before dpkg. This removes the
redundant COPY layer (31 instructions plus one base layer), without changing the
resulting runtime or its multi-stage build.
The affected performance check passes all 40 cases, including input rejection and
default-behavior preservation. Layer/wiring regressions and 46 packaging tests
pass. The previous publisher completed its other source checks and stopped on
this single stale literal; no image or tag was published.