perf(rpg): remove duplicate verification round trips #74
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/rpg-verification-round-trips"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Use the existing final metadata query to prove program and display-file existence. Keep the separate physical/logical data-file checks. This removes two or three redundant IBM i connections per Deploy. Move the metadata helper COPY to release-run so helper-only edits do not invalidate Build.
Cluster red/green proof: the actual Deploy runner rejects missing programs/modules/display files, source drift, missing Release evidence, SQL failure, and data-file mutations; it no longer makes duplicate CHKOBJ calls. A real BuildKit test with the actual old Dockerfile reproduced the unwanted Build rerun; the new Dockerfile reused the result after a helper edit. The test uses only synthetic source and credentials and does not contact IBM i or publish an image. make check and both runner/metadata test suites passed in the cluster.
No Binjovi core change. Release through Binjovi only.