Build manifests that want to compile 32-bit binaries can now
enable `gcc -m32` and the like with
```
packages:
- multilib-devel
```
instead of a task that patches pacman.conf.
Fedora 40 is now Fedora Rawhide and Fedora 39 is the branched release.
fedora/latest will be moved to fedora/39 when Fedora 39 is officially
released around October.
AuthContext.Grants is only populated for OAuth2 clients.
Use the new AuthContext.Access method to check for the SECRETS:RO
permission instead, to account for other auth kinds.
In a setup where internal traffic is meant to stay internal (i.e. the
`internal-origin` config is used) fetching logs is currently broken. The
logs are served by the api component, but as is the request will be sent
to the Python frontend.
Fix this by using the value of `api-origin`, just falling back to
`get_origin` if that is not set. This is the same technique already
employed in the Python GraphQL client.
Signed-off-by: Conrad Hoffmann <ch@bitfehler.net>
Submitting a build with secrets enabled grants access to secrets.
Let's reflect this in the token scope requirements.
In order to not break builds with no secrets argument specified,
make the default value a bit smarter: enable secrets if at least
one is specified in the manifest and the SECRETS:RO grant is
available.
Changes the error message for trying to run a non-existent architecture
to mention that it's specifically the architecture that's missing and
not the specific image (which is checked at the very start of the file).
The error message for a non-existent image is clarified a bit too, to
make it more clear what's wrong in the manifest, instead of how the
runner is detecting that.
This patch restores the status quo for the refresh jobs being visible
at https://builds.sr.ht/~sircmpwn/refresh from before builds.sr.ht
gained the concept of job visibility.
The --refresh flag is not supported by dnf5 which is now the default in
Fedora Rawhide. The fedora/rawhide image is completely broken without
this change.
* Add trixie as the new testing release.
* Update the testing,stable,oldstable aliases to point to the correct
distributions (trixie,bookworm,bullseye).
Duration histogram tracks the number of builds finished, and having
the number of builds running, number of builds started is trivial to
calculate, while having a gauge for currently running jobs makes it
easier to find current utilization. Additionally, a status label for
duration metric is added, to keep track of the distribution of different
build statuses that was kept by the builds finished metric.