Skip to content

Add native linux packaging#20

Merged
HereThereBeDragons merged 4 commits into
mainfrom
users/lpromber/main_add_native
Jan 23, 2026
Merged

Add native linux packaging#20
HereThereBeDragons merged 4 commits into
mainfrom
users/lpromber/main_add_native

Conversation

@HereThereBeDragons
Copy link
Copy Markdown
Contributor

First version to be able to build native linux packaging from rockrel.

While the name is build_native.. it has the same pattern as the release_.. we already have here: just invoking via workflow-dispatch the equivalent workflow in TheRock

@HereThereBeDragons
Copy link
Copy Markdown
Contributor Author

let me know if we just should add it only to 7.11 and not to main.

For TheRock, the needed PR for 7.11 is: ROCm/TheRock#3055
TheRock/main is missing those modifications (ref/repo)

Copy link
Copy Markdown
Member

@marbre marbre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First comments, needs a more careful review side-by-side to the upstream workflow.

ref:
description: "Branch, tag or SHA to checkout. Defaults to the reference or SHA that triggered the workflow."
type: string
default: main
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will break if triggered from a release branch and if someone forgets to set this. Furthermore, is does not match the description.

Suggested change
default: main

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i can adjust the description. so far we have added this default always to name the release branch. i thought it would be nice to just search for main and replace all for the new release?
what would you prefer? remove? or adjust description?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want to set a default, default: '' should work but pinning to main is probably not what we want here.

artifact_group: ${{ inputs.artifact_group }}
release_type: ${{ inputs.release_type }}
rocm_version: ${{ inputs.rocm_version }}
artifact_run_id: ${{ github.run_id }}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is actually a chance that we override packages as this uses the run_id in rockrel which is unique here but we could have had the same in TheRock. Needs to be addressed in a follow up.

Comment thread .github/workflows/build_native_linux_packages.yml
Copy link
Copy Markdown
Member

@marbre marbre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG to land as is and to allow further testing. Might need follow up changes upstream though.

@HereThereBeDragons HereThereBeDragons merged commit eae7587 into main Jan 23, 2026
1 check passed
@HereThereBeDragons HereThereBeDragons deleted the users/lpromber/main_add_native branch January 23, 2026 19:29
araravik-psd pushed a commit that referenced this pull request Jan 23, 2026
First version to be able to build native linux packaging from rockrel.

While the name is build_native.. it has the same pattern as the
release_.. we already have here: just invoking via workflow-dispatch the
equivalent workflow in TheRock
araravik-psd added a commit that referenced this pull request Jan 26, 2026
This PR is raised to cherry pick #20 from main to release branch and
also to pin build_native_linux_packages to release branch 7.11.

This will help build prereleases for 7.11

---------

Co-authored-by: Laura Promberger <lpromber@amd.com>
Co-authored-by: Aravind Ravikumar <arravikum@amd.com>
Co-authored-by: nunnikri <71024015+nunnikri@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants