ci.github: add preview-build workflow#6425
Conversation
497de85 to
5bb8e91
Compare
Does that syntax work? I thought you still had to provide it a list of objects for both the branch and the tags so something like: on:
push:
branches:
- master
tags-ignore:
- '**'
paths:
- "pyproject.toml"
- "setup.py"
- "MANIFEST.in"
- "build_backend/**"
- "src/**"per the documentation here (include) and here (exclude) |
5bb8e91 to
d16f06d
Compare
|
Thanks. True. No idea what I was thinking there... I also temporarily added a PR trigger to test the API permissions, and it looks like the permissions won't work (403 - "Resource not accessible by integration"). Going to have to use a PAT |
d16f06d to
1049231
Compare
1049231 to
be85ea7
Compare
|
PAT + write permissions added for @streamlinkbot (copy sent to [email protected]) Tested by running curl locally and building AppImages from this PR branch (we're only triggering workflows from the master branch however): Going to merge this now. Should be fine... Afterwards I'm going to delete the nightly build workflows from both repos. As said, old runs with their build artifacts should be kept until they expire. Btw, there's a known issue with GH's new public ubuntu-24.04-arm runners and their docker service, which sometimes fails to initialize and runners will sometimes fail randomly. |
|
The nightly CI workflow runs can't be selected anymore on the two repos, but their external links in the current stable docs are still working: |
Closes #6424
This new
preview-buildworkflow triggers thepreview-buildworkflows on thestreamlink/windows-buildsandstreamlink/streamlink-appimagerepos whenever something was pushed tomasterand eitherpyproject.toml,setup.py,MANIFEST.inorsrc/**was modified:These two links are added to the run's summary markdown text, so users can find the build artifacts easily when clicking the workflow here. Unfortunately, direct links in the summary can't be included, as the workflow here merely triggers the workflows on the other repos. GitHub doesn't include a workflow run ID in its API response.
The docs have also been updated accordingly. I will remove the nightly workflows from the repos after this PR here was merged. The recent runs and their build artifacts should remain for 90 days (until expiration) when deleting workflow files.
I've checked and triggered the workflows using a GH PAT, but I don't know if
secrets.GITHUB_TOKENwithpermissions.actions=writealso has the permissions to trigger a workflow on other repos. If it doesn't, then I will have to add a PAT for the @streamlinkbot and use that instead.Does the
on.pushconfig here look fine? Not 100% sure... Tags pushed should be ignored and the paths should be correct.