Skip to content

[CI] Record validation provenance for aggregate CI result - #504

Closed
brandonpage wants to merge 1 commit into
forcedotcom:devfrom
brandonpage:mobile-sdk-branch-rulesets
Closed

brandonpage wants to merge 1 commit into
forcedotcom:devfrom
brandonpage:mobile-sdk-branch-rulesets

Conversation

@brandonpage

Copy link
Copy Markdown
Contributor

Adds a terminal, per-attempt execution-provenance artifact to the PR validation entrypoint and an unfiltered PR integrity workflow. The aggregate publisher can verify the repository, PR, head/base commits, workflow revision, run and attempt without requiring individual matrix job names in branch rulesets.

The integrity workflow also provides initial metadata/syntax validation where no broad PR validation existed. Existing native CI remains part of the required validation policy.

This is a draft implementation. No ruleset is activated by these changes. Dedicated App installation, protected publisher deployment, workflow-ID enrollment, and live App/trust-boundary evidence are required before rollout. CI rulesets will remain in Evaluate mode.

Validation: generated workflows parse with PyYAML 6.0.4 and pass Actionlint 1.7.12; Zizmor 1.32.0 reports no findings in the new integrity workflows. Live Package fork fixtures verified successful provenance, pending/current reruns, rejection of an added workflow publishing an unrelated green CI result, and propagation of real validation failure. The App itself has not yet been installed or used to publish checks.

Publisher implementation: forcedotcom/SalesforceMobileSDK-Package#358

Target branch: dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant