Skip to content

Comments

[CI] Split build dependencies into own job on Windows#984

Open
jjhelmus wants to merge 3 commits intoastral-sh:mainfrom
jjhelmus:deps_ci
Open

[CI] Split build dependencies into own job on Windows#984
jjhelmus wants to merge 3 commits intoastral-sh:mainfrom
jjhelmus:deps_ci

Conversation

@jjhelmus
Copy link
Contributor

No description provided.

@jjhelmus jjhelmus added platform:windows Specific to the Windows platform python:3.12 arch:x86_64 labels Feb 20, 2026
persist-credentials: false

- name: Install Cygwin Environment
uses: cygwin/cygwin-install-action@f2009323764960f80959895c7bc3bb30210afe4d # v6

Check warning

Code scanning / zizmor

detects commit SHAs that don't match their version comment tags Warning

detects commit SHAs that don't match their version comment tags
@jjhelmus
Copy link
Contributor Author

This would be more useful if a matrix jobs could depend on a specific matrix job rather than the entire jobs to finish. In this way to x86-64+PGO Python builds could start as soon as the x86-64+PGO build-deps job finished rather than waiting for all matrix elements of build-deps to finish. This does not seem to be supported in GitHub Action but has been requested, https://github.com/orgs/community/discussions/42335.

outputs:
matrix: ${{ steps.set-matrix.outputs.matrix }}
crate-build-matrix: ${{ steps.set-matrix.outputs.crate-build-matrix }}
dep-build-matrix: ${{ steps.set-matrix.outputs.dep-build-matrix }}
Copy link
Member

Choose a reason for hiding this comment

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

nit: We generally prefer verbose names like "dependency" over short ones like "dep"

timeout-minutes: 90
needs:
- generate-matrix
# Permissions used for actions/attest-build-provenance
Copy link
Member

Choose a reason for hiding this comment

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

What is this comment referring to?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Left over copy and paste from the build job.

.\pythonbuild.exe validate-distribution --run $Dists

build-deps:
timeout-minutes: 90
Copy link
Member

Choose a reason for hiding this comment

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

90 minutes?

@zanieb
Copy link
Member

zanieb commented Feb 20, 2026

This would be more useful if a matrix jobs could depend on a specific matrix job rather than the entire jobs to finish. In this way to x86-64+PGO Python builds could start as soon as the x86-64+PGO build-deps job finished rather than waiting for all matrix elements of build-deps to finish. This does not seem to be supported in GitHub Action but has been requested, https://github.com/orgs/community/discussions/42335.

Hm that's indeed annoying. I guess you could also generate the workflow file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arch:x86_64 platform:windows Specific to the Windows platform python:3.12

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants