Repository navigation
ci: hand the BigLinux builders only the branches they can build - #14
Merged
Merged
Conversation
The BigLinux builders build a branch when a "Build Package" run of this repository ends in success; no dispatch is needed. Their public job history against this repository's runs shows it: main, testing-2026-10-07 and stable-2026-10-07 were built on 2026-10-07 by the workflow from 72fed17, which sent nothing, each at the minute its run succeeded. Two consequences, both since 2026-10-07: - notify-builders' repository_dispatch is refused (401 Bad credentials), which failed every push run, so main, testing-2026-10-07-1, -4 and testing-2026-10-08 were never built. - pull requests ran under the same name, so each successful one handed its fix/… branch over, and the builder's recipe broke on the '/' ("sed: unknown option to `s'", job 61686). notify-builders is removed. build-package.yml runs only for pushes to plain branch names and manual runs, and refuses a manual run of a branch with '/'. Pull requests (and manual checks of any branch) run the same job through workflow_call as package-check.yml, "Package check", which the builders do not act on. The CI audit says how the trigger was found.
Merged
ruscher
added a commit
to ruscher/bigamemode
that referenced
this pull request
Oct 9, 2026
pkgver, the workspace version and the AppStream release agree, as the package check requires. The release notes and the README's "What's new" cover what was merged since 2.3.0: - Turbo comes on without a falcond build that crashes on the processor (x86-64-v3 falcond on Sandy Bridge, Ivy Bridge), and that build is not started again until the package changes (#4, biglinux#12, biglinux#13); - a falcond that crashes at start is left disabled, and Turbo can be turned off after it (biglinux#12); - the Steam runtime's ldconfig is not taken for the game (biglinux#13); - fix commands with && no longer log a markup error (biglinux#13); - the BigLinux builders receive only the branches they can build (biglinux#14).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The BigLinux builders (gitlab.bigib.org/builder/packagebuilder) build a branch when a Build Package run of this repository ends in success. No dispatch is involved. Their public job history against this repository's runs:
main,testing-2026-10-07(workflow from72fed17, no dispatch step)stable-2026-10-07fix/github-actions-package-build(×2),fix/issue-4-…,fix/falcond-incompatible-build-fallbackfix/…handed over, the builder'ssedbreaks on/(job 61686)main(×2),testing-2026-10-07-1,-4,testing-2026-10-08notify-buildersgets 401 Bad credentialsSo
notify-builders(#11) stopped releases instead of restoring them, and pull requests handed theirfix/…branches to a recipe that cannot build them.Change
notify-buildersand its secret are removed.build-package.yml("Build Package"): pushes to plain branch names (main,testing-*,stable-*) and manual runs; a manual run of a branch with/fails at once.package-check.yml("Package check", new): the same job throughworkflow_call, for pull requests and manual runs of any branch; not handed to the builders.docs/ci-workflows-audit.mdand the README say how the trigger was found and how it works.This PR is itself the first check: it runs as Package check, and no
ci/…job should appear on the builder. After merging, the push tomainshould end in success and be followed by amainjob on the builder.testing-2026-10-08still carries the old workflow, so a release needs a new testing branch frommain.