From: "Magnus Granberg" <zorry@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/tinderbox-cluster:master commit in: buildbot_gentoo_ci/config/
Date: Sat, 30 Jul 2022 22:44:02 +0000 (UTC) [thread overview]
Message-ID: <1659221012.457eadb511be7e44744cfa4a91a302614b5d754f.zorry@gentoo> (raw)
commit: 457eadb511be7e44744cfa4a91a302614b5d754f
Author: Magnus Granberg <zorry <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 30 22:43:32 2022 +0000
Commit: Magnus Granberg <zorry <AT> gentoo <DOT> org>
CommitDate: Sat Jul 30 22:43:32 2022 +0000
URL: https://gitweb.gentoo.org/proj/tinderbox-cluster.git/commit/?id=457eadb5
Add scheduler_update_db_mr for mr/pr support
Signed-off-by: Magnus Granberg <zorry <AT> gentoo.org>
buildbot_gentoo_ci/config/schedulers.py | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/buildbot_gentoo_ci/config/schedulers.py b/buildbot_gentoo_ci/config/schedulers.py
index 2e5379c..b769f00 100644
--- a/buildbot_gentoo_ci/config/schedulers.py
+++ b/buildbot_gentoo_ci/config/schedulers.py
@@ -39,8 +39,15 @@ def getGitChanges(props):
change_data['revision'] = k['revision']
change_data['timestamp'] = k['when_timestamp']
change_data['branch'] = k['branch']
+ change_data['project'] = k['project']
return change_data
+def mr_branch_fn(branch):
+ # if branch end with -mr or -pr
+ if branch[-3] == '-mr' or branch[-3] == '-pr':
+ return True
+ return False
+
def gentoo_schedulers():
scheduler_update_db = schedulers.SingleBranchScheduler(
name='scheduler_update_db',
@@ -49,7 +56,16 @@ def gentoo_schedulers():
change_data = getGitChanges
),
builderNames = builderUpdateDbNames,
- change_filter=util.ChangeFilter(branch='master'),
+ change_filter=util.ChangeFilter(branch='master', category='push'),
+ )
+ scheduler_update_db_mr= schedulers.SingleBranchScheduler(
+ name='scheduler_update_db_mr',
+ treeStableTimer=0,
+ properties = dict(
+ change_data = getGitChanges
+ ),
+ builderNames = builderUpdateDbNames,
+ change_filter=util.ChangeFilter(branch_fn=mr_branch_fn, category='merge_request'),
)
create_stage4 = schedulers.ForceScheduler(
name="create_stage4",
@@ -86,6 +102,7 @@ def gentoo_schedulers():
s = []
s.append(create_stage4)
s.append(scheduler_update_db)
+ s.append(scheduler_update_db_mr)
s.append(update_repo_check)
s.append(update_cpv_data)
s.append(update_v_data)
next reply other threads:[~2022-07-30 22:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 22:44 Magnus Granberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-06 22:27 [gentoo-commits] proj/tinderbox-cluster:master commit in: buildbot_gentoo_ci/config/ Magnus Granberg
2023-06-10 10:08 Magnus Granberg
2023-06-05 8:09 Magnus Granberg
2023-05-28 9:49 Magnus Granberg
2023-05-28 9:49 Magnus Granberg
2023-05-01 9:58 Magnus Granberg
2022-08-10 21:51 Magnus Granberg
2022-07-28 11:35 Magnus Granberg
2022-07-13 19:53 Magnus Granberg
2022-06-11 9:52 Magnus Granberg
2022-06-01 0:19 Magnus Granberg
2022-04-22 12:32 Magnus Granberg
2022-01-24 0:49 Magnus Granberg
2022-01-08 17:22 Magnus Granberg
2021-10-27 20:08 Magnus Granberg
2021-10-16 14:56 Magnus Granberg
2021-04-04 20:30 Magnus Granberg
2021-04-02 22:12 Magnus Granberg
2021-02-27 22:46 Magnus Granberg
2021-02-24 21:27 Magnus Granberg
2020-12-30 9:18 Magnus Granberg
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=1659221012.457eadb511be7e44744cfa4a91a302614b5d754f.zorry@gentoo \
--to=zorry@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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