chore(ci): Reconfigure workflow triggers to push on master instead of waiting for the build-all workflow to complete

[LKreutzer]

Signed-off-by: Lars Kreutzer lars.kreutzer@tngtech.com

Summary

• Resolves Investigate and reconfigure integ test workflow triggers #13907
• Instead of waiting for the build-all job to complete the workflows are triggered by pushes/merges to the equivalent branches

Test Plan

Additional Information

• The deploy-build-from-pr workflow does indeed seem to require the build-all job.

• This change is backwards-breaking

[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 6b6185f.

♻️ This comment has been updated with latest results.

[Neudrino]

• Have you checked the respective fabfiles and makefile for the workflows if there is really no dependency on prebuild packages?
  • Did not do it for lte-integ-test-bazel and sudo-python-tests, because I believe you had a much closer look at them recently.
• Do a full text search for github.event_name and github.event.workflow_run in all workflows touched. Those parts will need an update as well.

[LKreutzer]

Replaced github.event.workflow_run.event == 'push' with github.event_name == 'push'

[LKreutzer]

Removed changes to .github/workflows/lte-integ-test-containerized.yml

[Neudrino]

Replaced github.event.workflow_run.event == 'push' with github.event_name == 'push'

I see that I would be a slight function change to not restrict it on push here, but do we really need to exclude the execution of those steps upon workflow_dispatch? If so, why?

[LKreutzer]

Replaced github.event.workflow_run.event == 'push' with github.event_name == 'push'

I see that I would be a slight function change to not restrict it on push here, but do we really need to exclude the execution of those steps upon workflow_dispatch? If so, why?

The steps that require a secret will fail if you run the workflow on a fork without the secrets.

[LKreutzer]

Replaced env.SHA with github.sha.