Skip to content

GitHub Workflow: Clean up CI workflow to avoid redundant work. - #655

Open
KimonHoffmann wants to merge 5 commits into
dmf-mxl:mainfrom
KimonHoffmann:feature/workflow_orthogonalization
Open

GitHub Workflow: Clean up CI workflow to avoid redundant work.#655
KimonHoffmann wants to merge 5 commits into
dmf-mxl:mainfrom
KimonHoffmann:feature/workflow_orthogonalization

Conversation

@KimonHoffmann

@KimonHoffmann KimonHoffmann commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Orthogonalize the CI workflow by separating out redundant steps that were previously lumped in with other variations.

Details

Backport requirements

None.
Beneficial to have on all active branches, so labels have been added accordingly.

Notes

Once this branch has been merged it is important to update the PR merge requirements & status checks for the newly structured CI steps (which is why this PR currently claims that 6 status checks are missing).

@KimonHoffmann
KimonHoffmann force-pushed the feature/workflow_orthogonalization branch 15 times, most recently from 1c87679 to 429baf4 Compare August 6, 2026 14:46
@KimonHoffmann KimonHoffmann linked an issue Aug 6, 2026 that may be closed by this pull request
@felixpou felixpou linked an issue Aug 6, 2026 that may be closed by this pull request
@felixpou felixpou mentioned this pull request Aug 6, 2026
@felixpou felixpou linked an issue Aug 6, 2026 that may be closed by this pull request
@KimonHoffmann
KimonHoffmann force-pushed the feature/workflow_orthogonalization branch 7 times, most recently from b7dbf21 to 4ba642c Compare August 7, 2026 10:22
@KimonHoffmann KimonHoffmann changed the title WIP: GitHub Workflow: Clean up CI workflow to avoid redundant work. GitHub Workflow: Clean up CI workflow to avoid redundant work. Aug 7, 2026

@vt-tv vt-tv left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not a github action expert by any means but I can't seem to find when/how the new reuse.yml workflow is invoked. I don't see any trace of it in the build logs.

@vt-tv vt-tv moved this to In progress in MXL TSC Board Aug 20, 2026
@KimonHoffmann

Copy link
Copy Markdown
Collaborator Author

I'm not a github action expert by any means but I can't seem to find when/how the new reuse.yml workflow is invoked. I don't see any trace of it in the build logs.

It is (now) a separate workflow with its separate trigger that runs independently of the CI build.

See
Bildschirmfoto 2026-09-01 um 12 48 24

@KimonHoffmann

Copy link
Copy Markdown
Collaborator Author

See also:
Bildschirmfoto 2026-09-01 um 12 50 48

@vt-tv vt-tv left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for this. LGTM

@vt-tv

vt-tv commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@KimonHoffmann should we backport to 1.1 or focus only on main? if so, please add the required labels.

@KimonHoffmann

Copy link
Copy Markdown
Collaborator Author

@KimonHoffmann should we backport to 1.1 or focus only on main? if so, please add the required labels.

We could, yes. I'll add the labels accordingly.

@KimonHoffmann KimonHoffmann added backport/v1.0 This PR should be back ported to the release branch of version 1.0. backport/v1.1 This PR should be back ported to the release branch of version 1.1. labels Sep 3, 2026
"

build_c_cxx:
name: Build C library on Ubuntu

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

While we are at it: All jobs render exactly the same name, and in the workflow run overview it is sometimes hard to see which one is which.

What about something like:

Build C/C++ on ${{ matrix.architecture }} - ${{ matrix.compiler }}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Hmmm, I removed the labels exactly, because the jobs already contain the matrix axes combination as part of their name?! (In parentheses, after the main title) Does that not render like that for you?

I found the redundant mention of the axes combination unpleasant and thus removed them.

echo "This pull request originates from the base repository."
echo "is-fork=false" >> "$GITHUB_OUTPUT"
fi
- name: Set up QEMU

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

With arm64 runners, do we still need qemu?

@KimonHoffmann KimonHoffmann Sep 8, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Not strictly, but having it available doesn't hurt and easily allows adding other architectures in the future that might not have dedicated runners available.

I also contemplated the removal, because I only switched to arm-native runners later in the refactor, making qemu obsolete. But for the reason above I opted to keep it around.

Comment thread .github/workflows/build.yml Outdated
Comment thread .github/workflows/build.yml Outdated
@KimonHoffmann
KimonHoffmann force-pushed the feature/workflow_orthogonalization branch from 4ba642c to 0b9c7bf Compare September 9, 2026 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/v1.0 This PR should be back ported to the release branch of version 1.0. backport/v1.1 This PR should be back ported to the release branch of version 1.1.

Projects

Status: In progress

3 participants