fix(ci): use correct variable offered by dispatch action

[ajahl]

Signed-off-by: Alex Jahl alexander.jahl@tngtech.com

Summary

#13983 uses a the wrong environment variable. The result is that the lte-integ-test-magma-deb workflow always install the latest magma package version in the magma debian vm.

magma/.github/workflows/build_all.yml

Line 1014 in 1bd2b73

client-payload: '{ "artifact": "${{ needs.agw-build.outputs.magma_package }}" }'

magma/.github/workflows/lte-integ-test-magma-deb.yml

Line 57 in 1bd2b73

MAGMA_PACKAGE: ${{ github.event.client_payload.magma_package }}

The lte-integ-test-magma-deb workflow uses magma_package in line 57 but needs artifact which is define in build-all in line 1014.

Test Plan

Can only be seen on the magma master branch after the PR is merged and the agw-build job in build-all run through.

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

dp-workflow

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 7b6e3f7.