Skip to content

.sync/Version.njk: Update linux_build_container to for 1.84.0 rust toolchain. #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 28, 2025
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .sync/Version.njk
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@
{% set previous_mu_release_branch = "release/202311" %}

{# The version of the ubuntu-24-build container to use. #}
{% set linux_build_container = "ghcr.io/microsoft/mu_devops/ubuntu-24-build:d412ccd" %}
{% set linux_build_container = "ghcr.io/microsoft/mu_devops/ubuntu-24-build:b089181" %}

{# The Python version to use. #}
{% set python_version = "3.12" %}
Expand Down
17 changes: 16 additions & 1 deletion ReadMe.rst
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,9 @@ Table of Contents

- `Submodule Release Updater`_

9. `Links`_
9. `Steps for Updating Rust Tool Chain`_

10. `Links`_

Continuous Integration (CI)
===========================
Expand Down Expand Up @@ -379,6 +381,19 @@ the GitHub action.

- `.sync/workflows/leaf/submodule-release-update.yml`

Steps for Updating Rust Tool Chain
=====================

Steps required to update the Rust tool chain in the Mu DevOps repo. The steps are as follows:

1. Update rust_toolchain in .sync/Version.njk to the new version.
2. Run Build Containers workflow to build a new linux container image (which will use updated .sync/Version.njk).
3. Update linux_build_container in .sync/Version.njk with the new version.
4. Create new mu_devops tag.
5. Update mu_devops in .sync/Version.njk to the newly generated tag.
6. Run Sync Mu DevOps Files to Mu Repos workflow to sync the new version to all Mu repos.
7. Complete associated PRs in the Mu repos.

Links
=====
- `Basic Azure Landing Site <https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops>`_
Expand Down