chore: bazel base image is pinned

[nstng]

Signed-off-by: Nils Semmelrock nils.semmelrock@tngtech.com

Summary

This is the first PR for #13755 (see merge strategy in issue).

Note: the devcontainer image in .github/workflows/agw-workflow.yml should not be relevant because no bazel builds are executed on that image.

Test Plan

• make sure correct sha is used - https://github.com/magma/magma/pkgs/container/magma%2Fbazel-base
• make sure all bazel base images in workflows are pinned

Additional Information

• 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 da8e861.

[LKreutzer]

Lgtm - I think the change in the agw workflow is relevant because the bazel coverage should also build the targeted services.

[nstng]

I think the change in the agw workflow is relevant because the bazel coverage should also build the targeted services.

Is this regarding

Note: the devcontainer image in .github/workflows/agw-workflow.yml should not be relevant because no bazel builds are executed on that image.

Or are you saying there is something missing?

The note is regarding the devcontainer image that is used in the agw workflow. The devcontainer is build on top of the bazel base image. Nevertheless, imo we do not need to pin it for this release strategy, because no bazel builds are executed on that image.

[LKreutzer]

The note is regarding the devcontainer image that is used in the agw workflow. The devcontainer is build on top of the bazel base image. Nevertheless, imo we do not need to pin it for this release strategy, because no bazel builds are executed on that image.

Nevermind - I did not see that you meant the devcontainer.

[github-actions]

agw-workflow

615 tests   611 ✔️  3m 44s ⏱️
    2 suites      4 💤
    2 files        0 ❌

Results for commit da8e861.