- Mar 06, 2025
-
-
Jarod Wilson authored
Its possible to get a None return from expected_signoff, so handle that by dropping in an error message instead. Signed-off-by:
Jarod Wilson <jarod@redhat.com> See merge request !1761
-
Jarod Wilson authored
At the moment, we filter all non-lead-stream backport attempts for CVE bugs, looking for a CVE tag in the y-stream commit. However, they're not always there, and if the z-stream issue has an explicit commit list in it, we should trust that. With this change, we're only doing filtering on a list of commits compiled by listing all the commits in a y-stream MR, in a fully automated backport attempt, where we likely do want to try to filter out any non-CVE commits from the series. So yeah, trust people when they provide an explicit commit list in jira for us. Fixes: #824 Signed-off-by:
Jarod Wilson <jarod@redhat.com> Closes #824 See merge request !1758
-
Jarod Wilson authored
Flag the kernel-ark os-build* branches with use_kerneloscope: false, since there isn't a kerneloscope tree for them, and we don't have jira branch matching support we'd need to find the right branch either. Signed-off-by:
Jarod Wilson <jarod@redhat.com> See merge request !1760
-
Jarod Wilson authored
We've seen some cases where a bogus commit ID is passed in, which doesn't result in a BadName exception, it results in a ValueError exception. We've already added this additional handling to the fixes hook, add it here too. Signed-off-by:
Jarod Wilson <jarod@redhat.com> See merge request !1762
-
Jarod Wilson authored
Flag the kernel-ark os-build* branches with use_kerneloscope: false, since there isn't a kerneloscope tree for them, and we don't have jira branch matching support we'd need to find the right branch either. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
- Mar 05, 2025
-
-
Jarod Wilson authored
Barebones skeleton web-hook used as a template for others to work off of Fixes: #566 Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com> Closes #566 See merge request !1675
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Jarod Wilson authored
We've seen some cases where a bogus commit ID is passed in, which doesn't result in a BadName exception, it results in a ValueError exception. We've already added this additional handling to the fixes hook, add it here too. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
In dev mode, it'll never actually leave a comment, but maybe people want to play around with it against staging and see how the comment stuff works. And we need to pass empty lists for label add/remove, rather than None, or the hook will crash. Signed-off-by:
Jarod Wilson <jarod@redhat.com> Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
And do a bit more data validation. Signed-off-by:
Jarod Wilson <jarod@redhat.com> Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Tyonnchie Berry authored
Barebones skeleton web-hook used as a template for others to work off of Fixes: #566 Signed-off-by:
Tyonnchie Berry <tyberry@redhat.com>
-
Jarod Wilson authored
Its possible to get a None return from expected_signoff, so handle that by dropping in an error message instead. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
- Mar 03, 2025
-
-
Jarod Wilson authored
This is just a commit to increase the coverage of the test case for jirahook webhook. There are several pieces of the code that are not being tested. Some simple checks in existing tests can solve that, but others require separated test cases. This is not part of #589 sub tasks but it could be. Signed-off-by:
Julio Faracco <jfaracco@redhat.com> See merge request !1599
-
Jarod Wilson authored
Signed-off-by:
Scott Weaver <scweaver@redhat.com> See merge request !1752
-
Jarod Wilson authored
At the moment, we filter all non-lead-stream backport attempts for CVE bugs, looking for a CVE tag in the y-stream commit. However, they're not always there, and if the z-stream issue has an explicit commit list in it, we should trust that. With this change, we're only doing filtering on a list of commits compiled by listing all the commits in a y-stream MR, in a fully automated backport attempt, where we likely do want to try to filter out any non-CVE commits from the series. So yeah, trust people when they provide an explicit commit list in jira for us. Fixes: #824 Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
Jarod Wilson authored
Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
Jarod Wilson authored
This makes it easier to update in future. The main reason is that current owners.yaml provides also list of users, while in old one you'd need to walk over all subsystems. Signed-off-by:
Jan Stancek <jstancek@redhat.com> See merge request !1757
-
Jarod Wilson authored
There's currently no dist-git policy for any rhivos branches, so with the distgit_ref for automotive source-git branches updated to point to the appropriate rhivos-* branches in dist-git, we're now failing policy checks. Add a per-branch flag to permit policy checks to pass w/no policy. Signed-off-by:
Jarod Wilson <jarod@redhat.com> See merge request !1754
-
Jan Stancek authored
Signed-off-by:
Jan Stancek <jstancek@redhat.com>
-
Jan Stancek authored
This makes it easier to update in future (and next commit). Signed-off-by:
Jan Stancek <jstancek@redhat.com>
-
- Feb 27, 2025
-
-
Jarod Wilson authored
There's currently no dist-git policy for any rhivos branches, so with the distgit_ref for automotive source-git branches updated to point to the appropriate rhivos-* branches in dist-git, we're now failing policy checks. Add a per-branch flag to permit policy checks to pass w/no policy. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
Jarod Wilson authored
This branch actually flows into rhivos-1-main in internal dist-git. Signed-off-by:
Jarod Wilson <jarod@redhat.com> See merge request !1753
-
Jarod Wilson authored
This branch actually flows into rhivos-1-main in internal dist-git. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
Michael Hofmann authored
This reverts commit 7c723699. Fixes #808 Signed-off-by:
Patrick Talbert <ptalbert@redhat.com> Closes #808 See merge request !1749
-
- Feb 26, 2025
-
-
Scott Weaver authored
Signed-off-by:
Scott Weaver <scweaver@redhat.com>
-
- Feb 25, 2025
-
-
Jarod Wilson authored
This is the initial commit of the elnhhook. In the time since I opened the original draft of the elnhook, it has changed. Now the hook monitors for new config MRs rather than trigger on the push event. I've kept the original MR description below because the push event code still exists but has been disabled for now. This webhook now evaluates MR events to determine if a new MR is a kernel-ark config MR and if so it will open an ELN Jira and update the MR description to include a JIRA tag. This hook can be tested using: ``` python3 -m webhook.elnhook --merge-request <gitlab-mr-link> ``` **v1 description:** _As it is written now, this hook will only open a jira issue when triggered by a config branch push event. That config branch is created by the current functionality running in the kernel-ark scheduled job. That job merges each day with the upstream kernel and adds any new configs that come in from upstream._ _In the future (as described in issue #770), this hook may take over some of the other functionality currently in kernel-ark which is why it triggers on a branch push event._ _I've been testing this using a fake push event that I initially took from [gitlab's webhook log](https://gitlab.com/cki-project/kernel-ark/-/hooks/5222317/hook_logs/10332764157)_ ``` $ python3 -m webhook.elnhook --json-message-file fake-push-event.json ``` Fixes: #770 Signed-off-by:
Scott Weaver <scweaver@redhat.com> Closes #770 See merge request !1712
-
Derek Barbosa authored
include RHEL11 and RHIVOS1. Cleanup some UI elements as well. Unify "strictness" for searching across "ALL" components. Signed-off-by:
Derek Barbosa <debarbos@redhat.com> See merge request !1750
-
Derek Barbosa authored
include RHEL11 and RHIVOS1. Cleanup some UI elements as well. Unify "strictness" for searching across "ALL" components. Signed-off-by:
Derek Barbosa <debarbos@redhat.com>
-
- Feb 20, 2025
-
-
Jarod Wilson authored
This does a few things... 1) Add .direnv to .gitignore, so we don't try to commit and push it 2) Add a bare-bones .envrc file, which has two load-if-exists for an /etc/kernel-workflow/envrc and a ~/.config/kernel-workflow/envrc additional env config file 3) Add a sample docs/kernel-workflow-envrc file that is more or less the snippet that was in the main README.md With these in place, we can further minimize the amount of copy-pasta people have to do, they just need to copy kernel-workflow-envrc into ~/.config/kernel-workflow/envrc and update it as needed, and things should Just Work(tm). Some of this is further prep work to make this easier to integrate into the rhel-developer-toolbox as a module, with just about everything auto-configured by ansible for you (including the quirky repos that some of the hooks need). [skip coverage check] Signed-off-by:
Jarod Wilson <jarod@redhat.com> See merge request !1735
-
Jarod Wilson authored
Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
- Feb 19, 2025
-
-
Jarod Wilson authored
This lets you invoke update-repo with an empty bucket name and fetch all the updates just using git, without ever touching awscli, should you so choose (which is what's currently happening in the RDTx module). It also adds a setup-remotes option to overlay all the remotes on top of a freshly cloned linus repo. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
Jarod Wilson authored
This does a few things... 1) Add .direnv to .gitignore, so we don't try to commit and push it 2) Add a bare-bones .envrc file, which has two load-if-exists for an /etc/kernel-workflow/envrc and a ~/.config/kernel-workflow/envrc additional env config file 3) Add a sample docs/kernel-workflow-envrc file that is more or less the snippet that was in the main README.md With these in place, we can further minimize the amount of copy-pasta people have to do, they just need to copy kernel-workflow-envrc into ~/.config/kernel-workflow/envrc and update it as needed, and things should Just Work(tm). Some of this is further prep work to make this easier to integrate into the rhel-developer-toolbox as a module, with just about everything auto-configured by ansible for you (including the quirky repos that some of the hooks need). Signed-off-by:
Jarod Wilson <jarod@redhat.com>
-
- Feb 18, 2025
-
-
Jarod Wilson authored
private part at: https://gitlab.cee.redhat.com/cki-project/deployment-all/-/merge_requests/3147 Signed-off-by:
Jan Stancek <jstancek@redhat.com> See merge request !1747
-
Patrick Talbert authored
This reverts commit 7c723699. Signed-off-by:
Patrick Talbert <ptalbert@redhat.com>
-