public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/buildbox] f45: Add Packit dist-git configuration
Date: Fri, 28 Aug 2026 00:38:43 GMT [thread overview]
Message-ID: <178787752328.1.3626264834864113844.rpms-buildbox-285158e85ce6@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/buildbox
Branch : f45
Commit : 285158e85ce6443a97997dbd94dc36a68e86c23d
Author : Javier Jardón <jjardon@gnome.org>
Date : 2026-08-27T21:16:10+01:00
Stats : +28/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/buildbox/c/285158e85ce6443a97997dbd94dc36a68e86c23d?branch=f45
Log:
Add Packit dist-git configuration
Automate rawhide release sync via pull_from_upstream.
Restrict tags to X.Y.Z so component tags (trexe-*, worker-*) are ignored.
Koji builds stay on rawhide; Bodhi updates cover branched
releases if those branches are added later.
---
diff --git a/.packit.yaml b/.packit.yaml
new file mode 100644
index 0000000..1a090d3
--- /dev/null
+++ b/.packit.yaml
@@ -0,0 +1,28 @@
+# See the documentation for more information:
+# https://packit.dev/docs/configuration/
+# https://packit.dev/docs/configuration/downstream_configuration_template
+# https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding
+
+upstream_project_url: https://gitlab.com/BuildGrid/buildbox/buildbox
+
+# Tags are bare versions (1.4.20), not v1.4.20.
+# Upstream also has component tags (trexe-*, worker-*); ignore those.
+upstream_tag_include: "^[0-9]+\\.[0-9]+\\.[0-9]+$"
+
+jobs:
+ # Requires Fedora mapping on https://release-monitoring.org/projects/
+ # and Monitoring enabled on https://src.fedoraproject.org/rpms/buildbox
+ - job: pull_from_upstream
+ trigger: release
+ dist_git_branches:
+ - fedora-rawhide
+
+ - job: koji_build
+ trigger: commit
+ dist_git_branches:
+ - fedora-rawhide
+
+ - job: bodhi_update
+ trigger: commit
+ dist_git_branches:
+ - fedora-branched
reply other threads:[~2026-08-28 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178787752328.1.3626264834864113844.rpms-buildbox-285158e85ce6@fedoraproject.org \
--to=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox