Conversation
See test results for failed build of commit 4d993609f1 |
|
@SaschaCowley - I think this has sufficient testing now, I have tested deployments for try builds. snapshots and releases to a local server. I think we should merge this before merging the server work, to ensure we have real life payloads being sent before receiving them. |
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the GitHub Actions pipeline to trigger on release tags, surface build metadata as outputs, compute and expose a launcher SHA256 checksum, and emit deployment webhooks for snapshot and production releases.
- Enabled
release-**tag triggers and switched togh releasecommands - Captured version and API metadata as job outputs
- Added steps to compute launcher SHA256 and deploy snapshots/releases via GitHub deployments API
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| ci/scripts/setBuildVersionVars.ps1 | Mark tagged builds as releases by setting release=1 |
| ci/README.md | Updated the Deploy section to reflect active steps |
| .github/workflows/testAndPublish.yml | Enabled release triggers, stored metadata outputs, updated artifact uploads, computed SHA256, and added snapshot/release deployment jobs |
Comments suppressed due to low confidence (2)
.github/workflows/testAndPublish.yml:248
- This step needs an explicit
id: uploadLauncherso that${{ steps.uploadLauncher.outputs.artifact-id }}inoutputswill resolve correctly.
uses: actions/upload-artifact@v4
.github/workflows/testAndPublish.yml:431
- [nitpick] You're computing a SHA1 hash here but elsewhere publishing a SHA256. For consistency, either switch to
sha256sumor rename this variable to indicate it is SHA1.
NVDA_HASH=$(sha1sum "$NVDA_EXE_NAME" | cut -d ' ' -f 1)
Fixup of #18244 Summary of the issue: Beta/rc snapshots will fail to deploy if there are merge conflicts between master and the snapshot commit. This will cause releases to be blocked, as we expect a passing beta/rc snapshot to perform the tagged release. Beta/rc don't need to have merge conflicts resolved to be a valid build, though regular merging to minimize these is ideal.
Link to issue number:
Part of #17878
Summary of the issue:
As part of migrating to GitHub actions, we need to deploy our signed snapshot/tagged builds to the server.
Description of developer facing changes:
The server can use that webhook to deploy releases.
Description of development approach:
switch to using
gh releaserather than a custom action for releasesDeploying
Testing strategy:
Tested releases triggered the webhook
Test a snapshot deployment to the server (locally)
Test a tagged release deployment to the server (locally)
Test a try build release deployment to the server (locally)
Known issues with pull request:
ci/README.mdneeds to be setup in this repoCode Review Checklist:
@coderabbitai summary