-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Integrate build_msi
into main CI workflow
#121778
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,24 @@ | ||||||
name: TestsMSI | ||||||
|
||||||
on: | ||||||
workflow_call: | ||||||
inputs: | ||||||
arch: | ||||||
description: CPU architecture | ||||||
required: true | ||||||
type: string | ||||||
|
||||||
permissions: | ||||||
contents: read | ||||||
|
||||||
jobs: | ||||||
build: | ||||||
name: installer for ${{ inputs.arch }} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't know if the name will be qualified in some other way?
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's already prefixed with "windows" on the calling side. I intentionally didn't add it here. The UI side is fine. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. On the screenshots above, it's visible that it's also consistent with other reusable workflows. |
||||||
runs-on: windows-latest | ||||||
timeout-minutes: 60 | ||||||
env: | ||||||
IncludeFreethreaded: true | ||||||
steps: | ||||||
- uses: actions/checkout@v4 | ||||||
- name: Build CPython installer | ||||||
run: .\Tools\msi\build.bat --doc -${{ inputs.arch }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@webknjaz Someone else has said "Tests / Windows MSI${{ '' }} (pull_request)" looks like a bug.
I think in some other thread you said we can adjust it somehow, is that possible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hugovk basically, there are two options:
I personally like the second option. Let me know if you or @ambv want something different.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though, I think both might break grouping 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, any other ideas? Someone else has asked about it because it looks weird.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be most impactful if GitHub fixed this in its own UI rather than having people resort to hacks. I'd be happy to drop the
${{ '' }}
hack from other places.Would it be less confusing is we switched
Windows MSI${{ '' }}
to${{ 'Windows MSI' }}
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would that look for the different builds?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same, just bits of syntax would be around the string, not after.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think that might be a bit better?
The recent query was actually about the
fromJSON
stuff, do you think we can do anything about that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicating the matrix or moving the conditional inside the reusable workflow would improve this, I suppose.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've done some thinking and realized that duplicating the matrices is the only way to make it look different while preserving the matrix grouping in the UI.