public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: pdancak <pdancak@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/xsane] rawhide: Update test/CI configuration files
Date: Mon, 07 Sep 2026 08:33:09 GMT	[thread overview]
Message-ID: <178876998987.1.15528319242823432918.rpms-xsane-74e1a3188276@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/xsane
            Branch : rawhide
            Commit : 74e1a31882761ddd7dfd952b682f51987c5548bf
            Author : pdancak <pdancak@redhat.com>
            Date   : 2026-09-04T14:59:48+02:00
            Stats  : +61/-0 in 4 file(s)
            URL    : https://src.fedoraproject.org/rpms/xsane/c/74e1a31882761ddd7dfd952b682f51987c5548bf?branch=rawhide

            Log:
            Update test/CI configuration files

Add or refresh test configuration on rawhide:
- .fmf/version
- gating.yaml
- plans.fmf
- ci.fmf

---
diff --git a/.fmf/version b/.fmf/version
new file mode 100644
index 0000000..d00491f
--- /dev/null
+++ b/.fmf/version
@@ -0,0 +1 @@
+1

diff --git a/ci.fmf b/ci.fmf
new file mode 100644
index 0000000..c5aa0e0
--- /dev/null
+++ b/ci.fmf
@@ -0,0 +1 @@
+resultsdb-testcase: separate

diff --git a/gating.yaml b/gating.yaml
new file mode 100644
index 0000000..82e4add
--- /dev/null
+++ b/gating.yaml
@@ -0,0 +1,24 @@
+--- !Policy
+product_versions:
+  - fedora-*
+decision_context: bodhi_update_push_testing
+subject_type: koji_build
+rules:
+  - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build./plans/tier1-public.functional}
+
+#Rawhide
+--- !Policy
+product_versions:
+  - fedora-*
+decision_context: bodhi_update_push_stable
+subject_type: koji_build
+rules:
+  - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build./plans/tier1-public.functional}
+
+#gating rhel
+--- !Policy
+product_versions:
+  - rhel-*
+decision_context: osci_compose_gate
+rules:
+  - !PassingTestCaseRule {test_case_name: osci.brew-build./plans/tier1-internal.functional}

diff --git a/plans.fmf b/plans.fmf
new file mode 100644
index 0000000..0f5e5bb
--- /dev/null
+++ b/plans.fmf
@@ -0,0 +1,35 @@
+/tier1-internal:
+  plan:
+    import:
+      url: https://gitlab.com/redhat/centos-stream/tests/xsane.git
+      name: /plans/tier1/internal
+
+/tier1-public:
+  plan:
+    import:
+      url: https://gitlab.com/redhat/centos-stream/tests/xsane.git
+      name: /plans/tier1/public
+
+/tier2-tier3-internal:
+  plan:
+    import:
+      url: https://gitlab.com/redhat/centos-stream/tests/xsane.git
+      name: /plans/tier2-tier3/internal
+
+/tier2-tier3-public:
+  plan:
+    import:
+      url: https://gitlab.com/redhat/centos-stream/tests/xsane.git
+      name: /plans/tier2-tier3/public
+
+/others-internal:
+  plan:
+    import:
+      url: https://gitlab.com/redhat/centos-stream/tests/xsane.git
+      name: /plans/others/internal
+
+/others-public:
+  plan:
+    import:
+      url: https://gitlab.com/redhat/centos-stream/tests/xsane.git
+      name: /plans/others/public

                 reply	other threads:[~2026-09-07  8:33 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=178876998987.1.15528319242823432918.rpms-xsane-74e1a3188276@fedoraproject.org \
    --to=pdancak@redhat.com \
    --cc=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