Skip to content

refactor: extract push-provenance to a script#164

Closed
keerthi-go wants to merge 1 commit into
mainfrom
refactor/push-provenance-script
Closed

refactor: extract push-provenance to a script#164
keerthi-go wants to merge 1 commit into
mainfrom
refactor/push-provenance-script

Conversation

@keerthi-go
Copy link
Copy Markdown
Contributor

Summary

Moves the 43-line Push provenance to qcom-distro-artifacts inline shell block out of qcom-release-reusable-workflow.yml into scripts/push-provenance.sh.

The workflow step becomes a single line:

- name: Push provenance to qcom-distro-artifacts
  if: ${{ !inputs.test-run }}
  env:
    GH_PAT: ${{ secrets.PAT }}
    SUITE: ${{ inputs.suite }}
    BOT_NAME: ${{ vars.DEB_PKG_BOT_CI_NAME }}
    BOT_EMAIL: ${{ vars.DEB_PKG_BOT_CI_EMAIL }}
  run: ./qcom-build-utils/scripts/push-provenance.sh

No behaviour change

All logic is identical — clones qcom-distro-artifacts, merges provenance JSON, pushes with 3-attempt rebase retry. All env vars unchanged. Script validates required vars at startup.

Move the 'Push provenance to qcom-distro-artifacts'
inline shell block (43 lines) into
scripts/push-provenance.sh.

The workflow step is now a single line:
  run: ./qcom-build-utils/scripts/push-provenance.sh

All env vars (GH_PAT, SUITE, BOT_NAME, BOT_EMAIL)
are unchanged. No behaviour change.

Signed-off-by: Keerthi Gowda <kbalehal@qti.qualcomm.com>
@keerthi-go
Copy link
Copy Markdown
Contributor Author

Superseded by #165 which combines both provenance scripts into one PR.

@keerthi-go keerthi-go closed this May 28, 2026
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