e625ee55f6
* Fix for hipother External CI pipeline (#3597) Recompilation of hip for AMD backend uses Microsoft-hosted agent, so no need to worry about VM costs if we re-build for any hipother repo changes. * Add a section on increasing memory allocation to the MI300A system op… (#3587) * Add a section on increasing memory allocation to the MI300A system optimization guide * Addition to wordlist * Change GB to GiB for consistency * Standardize GiB/KiB spacing * Minor wording changes * External CI: fix rocDecode CXX compiler (#3593) * External CI: enable clr and rocMLIR latestFromBranch downloads (#3604) * fix ROCdbgapi version number (#3605) * Update Compatibility Matrix for 6.2.0 (#3600) * add rocAL, hipCC, CLR. Rearrange order of some items to align with stack diagram. Update UCC versions * update llvm-project to point to docs page instead of GitHub * External CI: multi-gfx nightly ROCm builds (#3611) * External CI: create llvm symlink in all components (#3612) * External CI: Add hipBLAS-common to hipBLASLt dependency list (#3613) * add hipBLAS-common as dependency * add test variables * revert test variable * Build(deps): Bump rocm-docs-core from 1.7.0 to 1.7.1 in /docs/sphinx (#3614) Bumps [rocm-docs-core](https://github.com/ROCm/rocm-docs-core) from 1.7.0 to 1.7.1. - [Release notes](https://github.com/ROCm/rocm-docs-core/releases) - [Changelog](https://github.com/ROCm/rocm-docs-core/blob/develop/CHANGELOG.md) - [Commits](https://github.com/ROCm/rocm-docs-core/compare/v1.7.0...v1.7.1) --- updated-dependencies: - dependency-name: rocm-docs-core 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> * External CI: add hipBLAS-common to MIOpen (#3616) * External CI: make llvm-project symlink optional (#3617) * External CI: Pipeline dependency adjustments for hipBLAS-common (#3618) * External CI: use root disk for ROCm nightly build (#3619) * External CI: fix HIP pipeline ID for copyHIP (#3620) * Add rocPyDecode with other changes (#3609) --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Joseph Macaranas <145489236+amd-jmacaran@users.noreply.github.com> Co-authored-by: Jeffrey Novotny <jnovotny@amd.com> Co-authored-by: Daniel Su <danielsu@amd.com> Co-authored-by: Peter Park <peter.park@amd.com> Co-authored-by: alexxu-amd <159800977+alexxu-amd@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: randyh62 <42045079+randyh62@users.noreply.github.com>
ROCm-CI Azure DevOps Pipelines
ROCm-CI Azure DevOps Pipelines contains markup language files that orchestrate build and test pipelines for ROCm components using Azure DevOps.
Project Organization
/.azuredevops/variables-global.yml- set of global variables accessible across any and all pipelines- protected keywords such as tokens and passwords are kept as secrets within the Azure DevOps project
/.azuredevops/components- the sequence of templated steps for the job that checks out source, builds, packages, and runs tests for a ROCm repo/.azuredevops/scheduled- the sequence of templated steps for jobs that are schedule-based and not tied to a specific ROCm repo/.azuredevops/tag-builds- yml files to orchestrate manual builds based on specific tags (e.g., releases) without needing the corresponding yaml file in the component's repo/.azuredevops/templates- reusable yml files representing the templated steps that form the sequences in the above directories
Per ROCm Repo
/.azuredevops/rocm-ci.yml- contains the CI and PR trigger definitions associated with that repo, pointing to the corresponding yml file in the components folder in this central repository
Key Azure Reference Links
Disclaimer
The information presented in this document is for informational purposes only and may contain technical inaccuracies, omissions, and typographical errors. The information contained herein is subject to change and may be rendered inaccurate for many reasons, including but not limited to product and roadmap changes, component and motherboard versionchanges, new model and/or product releases, product differences between differing manufacturers, software changes, BIOS flashes, firmware upgrades, or the like. Any computer system has risks of security vulnerabilities that cannot be completely prevented or mitigated.AMD assumes no obligation to update or otherwise correct or revise this information. However, AMD reserves the right to revise this information and to make changes from time to time to the content hereof without obligation of AMD to notify any person of such revisions or changes.THIS INFORMATION IS PROVIDED ‘AS IS.” AMD MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE CONTENTS HEREOF AND ASSUMES NO RESPONSIBILITY FOR ANY INACCURACIES, ERRORS, OR OMISSIONS THAT MAY APPEAR IN THIS INFORMATION. AMD SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AMD BE LIABLE TO ANY PERSON FOR ANY RELIANCE, DIRECT, INDIRECT, SPECIAL, OR OTHER CONSEQUENTIAL DAMAGES ARISING FROM THE USE OF ANY INFORMATION CONTAINED HEREIN, EVEN IF AMD IS EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. AMD, the AMD Arrow logo, and combinations thereof are trademarks of Advanced Micro Devices, Inc. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
© 2024 Advanced Micro Devices, Inc. All Rights Reserved.