Skip to content

[Ex CI] update release-staging workflows#612

Merged
danielsu-amd merged 4 commits into
release-staging/rocm-rel-7.0from
users/danielsu/release-update-az-ci
Jul 11, 2025
Merged

[Ex CI] update release-staging workflows#612
danielsu-amd merged 4 commits into
release-staging/rocm-rel-7.0from
users/danielsu/release-update-az-ci

Conversation

@danielsu-amd
Copy link
Copy Markdown
Contributor

@danielsu-amd danielsu-amd commented Jul 11, 2025

Depends on ROCm/ROCm#5033

Creates a trigger file for hipSPARSELt in the monorepo. hipSPARSELt will
be part of rocBLAS's downstream jobs until hipSPARSE is migrated into
the monorepo.

In azure_resolve_subtree_deps.py:
- Added entry in dep tree for hipSPARSELt depending on hipSPARSE
- Added pipeline ID for new hipSPARSELt pipeline
- Fix the `resolve_dependencies()` function to fully recurse over the
dependency tree instead of only checking 1 level deep
- Fix incorrect deps for rocSOLVER and rocSPARSE
- Fix inconsistent capitalization in dep tree
Progress for #479

Reworks the Azure dispatch action to be nonpolling, which resolves the
360 minute timeout issue. It now creates a separate `Azure CI Summary`
check, which will be updated inside Azure pipeline runs via the
`report-summary-check.yml` template. This summary check is intended to
be marked as required.

Once an Azure pipelines run finishes, it will report its overall status
to the summary. If any jobs have failed or are cancelled, the summary
check will be marked as failed. If all jobs have succeeded, the summary
will pass.

Adds logic for handling rerunning the initial dispatch action, which
will either start new runs or rerun existing runs depending on the state
of the PR. Instructions for doing so are included directly in the
summary checks for easy access.

Overview of flow:
1. PR is created, `Trigger Azure CI` action is run on PR
2. `Trigger Azure CI` kicks off Azure runs and creates an `Azure CI
Summary` check
3. As Azure runs finish, `Azure CI Summary` is updated with their
statuses
4. After all runs are finished, `Azure CI Summary` will be marked as
successful or failed depending on the runs' statuses
5. If a rerun is desired, `Trigger Azure CI` can be rerun, which will
overwrite the existing `Azure CI Summary` with a new one

Sample runs:
Branch PR: #561 -
[summary](https://github.com/ROCm/rocm-libraries/pull/561/checks?check_run_id=45813198366)
Fork PR: #600 -
[summary](https://github.com/ROCm/rocm-libraries/pull/600/checks?check_run_id=45815418773)

Other stuff:
- Copied the Github CLI fallback logic from `pr_category_label.py` to
`pr_detect_changed_subtrees.py`
  - To fix dispatch action not running on PRs with infinite diffs
- Removed `paths-ignore` from dispatch action
@danielsu-amd danielsu-amd merged commit 60eca57 into release-staging/rocm-rel-7.0 Jul 11, 2025
6 checks passed
@danielsu-amd danielsu-amd deleted the users/danielsu/release-update-az-ci branch July 11, 2025 21:29
ammallya pushed a commit that referenced this pull request Jul 22, 2025
Bumps [rocm-docs-core](https://github.com/ROCm/rocm-docs-core) from 1.18.2 to 1.18.4.
- [Release notes](https://github.com/ROCm/rocm-docs-core/releases)
- [Changelog](https://github.com/ROCm/rocm-docs-core/blob/develop/CHANGELOG.md)
- [Commits](ROCm/rocm-docs-core@v1.18.2...v1.18.4)

---
updated-dependencies:
- dependency-name: rocm-docs-core
  dependency-version: 1.18.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

[ROCm/hipSPARSE commit: 462f240]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants