Use python-jira to abstract the API authentication, matching most of what is used by KWF.

Closes: #294

[skip coverage check] because I'm breaking and disabling sprinter/jira_mirror tests, but jira.py is fully covered

Signed-off-by: Tales da Aparecida [email protected]

🤖 AI Code Review

✅ AI analysis complete - Review details below

AI Code Review

📋 MR Summary

Transitions Jira interactions in umb_messenger to use the python-jira library, enabling Jira Cloud support.

• Key Changes:
  • Replaced manual HTTP requests to Jira API with the python-jira client.
  • Updated authentication to use Basic Auth (Email + Token) required for Jira Cloud.
  • Updated the QA contact custom field ID to match the Jira Cloud instance.
  • Added jira to project dependencies and updated tests to mock python-jira behavior.
• Impact: cki_tools/umb_messenger/jira.py, pyproject.toml, tests/test_umb_messenger.py, tests/sprinter/test_jira_mirror.py
• Risk Level: 🟢 Low - The changes are well-contained within the umb_messenger module and properly tested. The intentional disabling of sprinter tests is acknowledged and accepted per the PR context.

Detailed Code Review

The transition to python-jira is implemented cleanly and aligns with the project's goal of standardizing Jira interactions. The use of lru_cache for the client singleton is a good approach, and the test coverage has been appropriately updated to handle the new library's internal requests.

No critical issues or bugs were identified in the implementation. The error handling implicitly relies on JIRAError bubbling up, which is consistent with the previous behavior where requests.exceptions.HTTPError would bubble up due to raise_for_status=True.

✅ Summary

• Overall Assessment: The implementation is solid, correctly abstracts the Jira API, and meets the requirements for Jira Cloud support. No critical issues were found.
• Minor Suggestions:
  • Consider wrapping the jira_client.search_issues call in a try/except block to catch JIRAError and log a warning if you want to prevent transient Jira API failures from crashing the entire message processing pipeline, though bubbling up may be the intended behavior.

---

🤖 AI Code Review | Generated with ai-code-review | Model: gemini-3.1-pro-preview

⚠️ AI-generated suggestions may be incorrect. Verify before applying. Not a replacement for human review.

Group	Branch	ID	Status
centos	c9s	2389459424	✔️ success

See the welcome message for details on how to run tests more selectively.

1. Updated 2026-03-17 05:16 UTC by gitlab-ci-bot - Slack #team-kernel-cki - Source - Documentation - Report an issue ¹ ↩

@cki-ci-bot test [centos/c9s][architecture=x86_64][debug_architectures=][tests_only=False]

habib, try to trigger a few more pipelines until you are convinced you are activating all changed code

Hi! This is the friendly CKI test bot.

Everybody with developer access can mention me in a top-level comment together with test [PIPELINES] and I will test this merge request. Once the testing is done, I will post the results here.

Click here for details on how to select the tests to run.

The testing is done by retriggering formerly successful pipelines with the new code. Pipelines are specified by [GROUP/BRANCH] or [GROUP/PIPELINE-ID].

The following pipeline groups are configured:

• [ark]: kernel-ark pipelines (tests that involve kernel-ark kernels)
• [upstream]: Upstream kernel pipelines (tests that involve upstream kernels)
• [gcov]: RHEL ystream gcov pipelines (RHEL ystream baseline with code coverage)
• [centos-gcov]: CKI CentOS Stream gcov pipelines (CentOS Stream baseline with code coverage)
• [centos]: CKI CentOS Stream pipelines (CentOS Stream baseline)
• [rhel]: CKI RHEL pipelines (RHEL baseline pipeline for ystreams and zstreams)
• [scratch]: CKI Scratch pipelines (RHEL scratch pipeline for ystreams and zstreams)
• [koji]: Koji pipelines (tests involving Koji)
• [public]: limited pipelines (public limited runs)

Within these groups, the following branches are configured:

• [ark/eln]
• [ark/eln/debug]
• [ark/eln/64k]
• [ark/eln/64k-debug]
• [ark/eln/rt]
• [ark/eln/rt-debug]
• [ark/rawhide]
• [ark/rawhide/debug]
• [ark/rawhide/16k]
• [ark/rawhide/16k-debug]
• [ark/rawhide/clang]
• [ark/rawhide/clang-debug]
• [ark/rawhide/clanglto]
• [ark/rawhide/clanglto-debug]
• [upstream/mainline]
• [upstream/mainline-clang]
• [gcov/rhel-8/8.2]
• [gcov/rhel-8/8.4]
• [gcov/rhel-8/8.6]
• [gcov/rhel-8/8.8]
• [gcov/rhel-8/main]
• [gcov/rhel-8]
• [gcov/rhel-9/9.0]
• [gcov/rhel-9/9.2]
• [gcov/rhel-9/9.4]
• [gcov/rhel-9/9.6]
• [gcov/rhel-9/9.7]
• [gcov/rhel-9/9.8]
• [gcov/rhel-10/10.0]
• [gcov/rhel-10/10.0-beta]
• [gcov/rhel-10/10.1]
• [gcov/rhel-10/10.2]
• [gcov/rhel-10/10.2-ivos-qualcomm]
• [centos-gcov/c9s]
• [centos-gcov/c9s-auto]
• [centos/c9s]
• [centos/c9s-auto]
• [centos/c9s/64k]
• [centos/c9s/rt]
• [centos/c9s/rt-64k]
• [centos/c10s]
• [centos/c10s/debug]
• [centos/c10s/64k]
• [centos/c10s/64k-debug]
• [centos/c10s/rt]
• [centos/c10s/rt-debug]
• [centos/c10s/rt-64k]
• [centos/c10s/rt-64k-debug]
• [rhel/rhel-6/main]
• [rhel/rhel-6]
• [rhel/rhel-7/7.6]
• [rhel/rhel-7/7.7]
• [rhel/rhel-7/main]
• [rhel/rhel-7]
• [rhel/rhel-8/8.2]
• [rhel/rhel-8/8.4]
• [rhel/rhel-8/8.6]
• [rhel/rhel-8/8.8]
• [rhel/rhel-8/main]
• [rhel/rhel-8]
• [rhel/rhel-9/9.0]
• [rhel/rhel-9/9.2]
• [rhel/rhel-9/9.4]
• [rhel/rhel-9/9.6]
• [rhel/rhel-9/9.7]
• [rhel/rhel-9/9.8]
• [rhel/rhel-10/10.0]
• [rhel/rhel-10/10.0-beta]
• [rhel/rhel-10/10.1]
• [rhel/rhel-10/10.2]
• [rhel/rhel-10/10.2-ivos-qualcomm]
• [rhel/rhel-10/10.0/debug]
• [rhel/rhel-10/10.0-beta/debug]
• [rhel/rhel-10/10.1/debug]
• [rhel/rhel-10/10.2/debug]
• [rhel/rhel-10/10.2-ivos-qualcomm/debug]
• [rhel/rhel-9/9.2/64k]
• [rhel/rhel-9/9.4/64k]
• [rhel/rhel-9/9.6/64k]
• [rhel/rhel-9/9.7/64k]
• [rhel/rhel-9/9.8/64k]
• [rhel/rhel-10/10.0/64k]
• [rhel/rhel-10/10.0-beta/64k]
• [rhel/rhel-10/10.1/64k]
• [rhel/rhel-10/10.2/64k]
• [rhel/rhel-10/10.2-ivos-qualcomm/64k]
• [rhel/rhel-10/10.0/64k-debug]
• [rhel/rhel-10/10.0-beta/64k-debug]
• [rhel/rhel-10/10.1/64k-debug]
• [rhel/rhel-10/10.2/64k-debug]
• [rhel/rhel-10/10.2-ivos-qualcomm/64k-debug]
• [rhel/rhel-7/main/rt]
• [rhel/rhel-7/rt]
• [rhel/rhel-8/main/rt]
• [rhel/rhel-8/rt]
• [rhel/rhel-9/9.0/rt]
• [rhel/rhel-9/9.2/rt]
• [rhel/rhel-9/9.4/rt]
• [rhel/rhel-9/9.6/rt]
• [rhel/rhel-9/9.7/rt]
• [rhel/rhel-9/9.8/rt]
• [rhel/rhel-10/10.0/rt]
• [rhel/rhel-10/10.0-beta/rt]
• [rhel/rhel-10/10.1/rt]
• [rhel/rhel-10/10.2/rt]
• [rhel/rhel-10/10.2-ivos-qualcomm/rt]
• [rhel/rhel-10/10.0/rt-debug]
• [rhel/rhel-10/10.0-beta/rt-debug]
• [rhel/rhel-10/10.1/rt-debug]
• [rhel/rhel-10/10.2/rt-debug]
• [rhel/rhel-10/10.2-ivos-qualcomm/rt-debug]
• [rhel/rhel-10/10.0/rt-64k-debug]
• [rhel/rhel-10/10.0-beta/rt-64k-debug]
• [rhel/rhel-10/10.1/rt-64k-debug]
• [rhel/rhel-10/10.2/rt-64k-debug]
• [rhel/rhel-10/10.2-ivos-qualcomm/rt-64k-debug]
• [rhel/rhel-10/10.0/automotive]
• [rhel/rhel-10/10.0-beta/automotive]
• [rhel/rhel-10/10.1/automotive]
• [rhel/rhel-10/10.2/automotive]
• [rhel/rhel-10/10.2-ivos-qualcomm/automotive]
• [rhel/rhel-10/10.0/automotive-debug]
• [rhel/rhel-10/10.0-beta/automotive-debug]
• [rhel/rhel-10/10.1/automotive-debug]
• [rhel/rhel-10/10.2/automotive-debug]
• [rhel/rhel-10/10.2-ivos-qualcomm/automotive-debug]
• [rhel/rhel-9/main]
• [rhel/rhel-9]
• [rhel/rhel-10/main]
• [rhel/rhel-10]
• [scratch/rhel-7]
• [scratch/rhel-8]
• [scratch/rhel-9]
• [scratch/rhel-10]
• [koji/fedora]
• [koji/eln]
• [koji/eln/debug]
• [koji/eln/64k]
• [koji/eln/64k-debug]
• [public/kernel-ark]

When triggering a pipeline for a branch, the last successful pipeline is retriggered.

The precise bot configuration can be found in cee/deployment-all.

Click here for details on how to adjust the functionality of the retriggered pipeline by replacing the trigger variables of the original pipeline.

Variables can be replaced by specifying [name=value] in the test command:

• Only run the pipeline for x86_64 and s390x: [architectures=x86_64 s390x]
• Run pipeline for debug kernels for x86_64 and aarch64: [debug_architectures=x86_64 aarch64]
• Use the latest container images: [image_tag=latest]
• Run the tests in Beaker (please use this functionality responsibly and conserve the resources if the test runs are not needed): [skip_beaker=false]
• Force a full pipeline via [tests_only=false] or a short pipeline with only the setup and testing stages via [tests_only=true].
• Code coverage analysis:
  • For RHEL, please use [gcov/<branch>][skip_beaker=false]
  • For CentOS, please use [centos-gcov/<branch>][skip_beaker=false], with the appropriate branch (c9s, c9s-auto)
  • To limit coverage to certain kernel directories add [coverage_dirs=dirs1 dirs2].
• Limited test set: [test_set=net]
• Filter test names (bot uses raw comment so don't escape special characters): [tests_regex=.*Networking ipsec.*]
• Force an MR run with targeted testing: [force_baseline=false]
• If needed, a closing square bracket can be specified by \u005D

The full list of available variables can be found in the CKI documentation.

Click here for details on how to test multiple merge requests across different projects at the same time.

When testing a single merge request, a corresponding override variable is automatically added to the trigger variables. To test multiple merge requests, the corresponding override variables for the other merge requests must be added manually:

Project	Variable
beaker-jobwatch	[beaker_jobwatch_pip_url=git+https://gitlab.com/redhat/centos-stream/tests/kernel/beaker-jobwatch.git/@refs/merge-requests/123/merge]
cki-lib	[cki_lib_pip_url=git+https://gitlab.com/cki-project/cki-lib.git/@refs/merge-requests/123/merge]
cki-tools	[cki_tools_pip_url=git+https://gitlab.com/cki-project/cki-tools.git/@refs/merge-requests/123/merge]
containers	[image_tag=mr-123]
kpet	[kpet_pip_url=git+https://gitlab.com/cki-project/kpet.git/@refs/merge-requests/123/merge]
kpet-db	[kpet_db_pip_url=git+https://gitlab.com/redhat/centos-stream/tests/kernel/kpet-db.git/@refs/merge-requests/123/merge]
pipeline-definition	[pipeline_definition_branch_override=refs/merge-requests/123/merge]
reporter	[reporter_pip_url=git+https://gitlab.com/cki-project/reporter.git/@refs/merge-requests/123/merge]
upt	[upt_pip_url=git+https://gitlab.com/cki-project/upt.git/@refs/merge-requests/123/merge]

For more details about the features, check out the bot documentation.

1. Created 2026-03-17 03:30 UTC by gitlab-ci-bot - Slack #team-kernel-cki - Source - Documentation - Report an issue ¹ ↩

Use python-jira to abstract the API authentication, matching most of what is used by KWF.

Closes: #294

[skip coverage check] because I'm breaking and disabling sprinter/jira_mirror tests, but jira.py is fully covered

Signed-off-by: Tales da Aparecida [email protected]

updated

Affected subsystem(s): redhat, block, cpufreq, base, phylib, gpu, pwm

Requesting review of subsystem redhat with 1 required approval(s) from user(s) @clrkwllms ([email protected]) @debarbos ([email protected]) @dzickusrh ([email protected]) @ezulian ([email protected]) @hertonrk-rh ([email protected]) @jmflinuxtx ([email protected]) @jstancek ([email protected]) @jwilsonrh ([email protected]) @jwyatt-rh ([email protected]) @lgoncalv ([email protected]) @prarit ([email protected]) @ptalbert ([email protected])

Requesting review of subsystem block with 0 required approval(s) from user(s) @jmoyer1 ([email protected]) @minlei ([email protected]) @vgoyal ([email protected])

Requesting review of subsystem cpufreq with 1 required approval(s) from user(s) @darcari ([email protected]) @lszubowi ([email protected]) @mlangsdorf ([email protected]) @prarit ([email protected]) @sfbest ([email protected])

Requesting review of subsystem base with 0 required approval(s) from user(s) @mlangsdorf ([email protected])

Requesting review of subsystem phylib with 1 required approval(s) from user(s) @ibakolla ([email protected]) @ivecera ([email protected]) @jtornosm ([email protected]) @kheib ([email protected]) @mschmidt2 ([email protected]) @poros2 ([email protected]) @vinschen ([email protected])

Requesting review of subsystem gpu with 1 required approval(s) from user(s) @Lyude ([email protected]) @airlied ([email protected]) @asrivats1 ([email protected]) @da_kr ([email protected]) @daenzer ([email protected]) @ernunes ([email protected]) @jexposit ([email protected]) @karolherbst ([email protected]) @kdj0c ([email protected]) @martinezjavier ([email protected]) @mpenttil ([email protected]) @mripard ([email protected]) @nwnk ([email protected]) @robertfoss ([email protected])

Requesting review of subsystem pwm with 0 required approval(s) from user(s) @jasowers ([email protected])

1. Created 2026-03-16 23:51 UTC by ack_nack - KWF FAQ - Slack #team-kernel-workflow - Source - Documentation - Report an issue ¹ ↩

The actual filter contains both project = RHEL and component in componentMatch("^kernel($| / .*$)")

Kernel Configuration Evaluation: ConfigsOK

This report indicates how any detected Kconfig changes compare with expected changes in the merged .config and with the ARK configs.

The Kconfig evaluation is not blocking at this time. If the results appear to be incorrect, please notify the KWF team in slack #team-kernel-workflow or via a jira issue in the KMAINT project.

This Merge Request has no detected kernel config changes in it.

To request re-evalution after resolving any issues with the configs in the merge request, add a comment to this MR with only the text: request-configs-evaluation

1. Created 2026-03-16 22:34 UTC by configshook - KWF FAQ - Slack #team-kernel-workflow - Source - Documentation - Report an issue ¹ ↩

The saved filter in question:

https://redhat.atlassian.net/issues/?filter=104740

Related: KMAINT-2137

Signed-off-by: Jarod Wilson [email protected]

Mergeability Summary: MergeOK

This MR can be merged cleanly to its target branch.

1. Updated 2026-03-16 22:20 UTC by mergehook - KWF FAQ - Slack #team-kernel-workflow - Source - Documentation - Report an issue ¹ ↩

Don't we currently build ELN with_realtime? Just because we are also building a realtime kernel, we still want all of the other regular variants to build. I would expect similar behavior if someone were to choose to build Fedora realtime. I expect this should be the difference between with_realtime and with_rtonly.

ACK/NACK Summary: AcksNeedsReview

Required Approvals:

• Approval Rule "redhat" requires at least 1 ACK(s) (0 given) from set (debarbos, dzickusrh, ezulian, hertonrk-rh, jmflinuxtx, jstancek, jwilsonrh, jwyatt-rh, lgoncalv, prarit, ptalbert, scweaver).

Requires 1 more Approval(s).

1. Created 2026-03-16 22:10 UTC by ack_nack - KWF FAQ - Slack #team-kernel-workflow - Source - Documentation - Report an issue ¹ ↩

Affected subsystem(s): redhat

Requesting review of subsystem redhat with 1 required approval(s) from user(s) @debarbos ([email protected]) @dzickusrh ([email protected]) @ezulian ([email protected]) @hertonrk-rh ([email protected]) @jmflinuxtx ([email protected]) @jstancek ([email protected]) @jwilsonrh ([email protected]) @jwyatt-rh ([email protected]) @lgoncalv ([email protected]) @prarit ([email protected]) @ptalbert ([email protected]) @scweaver ([email protected])

1. Created 2026-03-16 22:10 UTC by ack_nack - KWF FAQ - Slack #team-kernel-workflow - Source - Documentation - Report an issue ¹ ↩

CommitRules Check Report CommitRulesOK

CommitRules Check for all commits and the MR description has PASSED.

1. Created 2026-03-16 22:10 UTC by signoff - KWF FAQ - Slack #team-kernel-workflow - Source - Documentation - Report an issue ¹ ↩

CKI Pipelines Status: CKIOK

Summary

All required pipelines have passed!

Pipeline	State
64K Debug	OK
64K	OK
Automotive Debug	OK
Automotive	OK
CentOS	OK
Debug	OK
ELN 64K Debug	OK
ELN 64K	OK
ELN Debug	OK
ELN Realtime 64K Debug	OK
ELN Realtime 64K	OK
ELN Realtime Debug	OK
ELN Realtime	OK
ELN	OK
Rawhide 16K Debug	OK
Rawhide 16K	OK
Rawhide Debug	OK
Rawhide	OK
Realtime 64K Debug	OK
Realtime 64K	OK
Realtime Debug	OK
Realtime	OK

1. Updated 2026-03-16 23:55 UTC by ckihook - CKI FAQ - Slack #team-kernel-cki - Source - Documentation - Report an issue ¹ ↩

This is a set of specfile changes which allow setting the with_rtonly variable and consequently building only the x86_64 and aarch64 kernel-rt variants.

Changes for when with_rtonly=1:

• only turn off debuginfo for unsupported arches (need BTF info)
• use nobuildarches for omitting RT on unsupported arches
• guard stock build with !with_rtonly
• force with_rt_base=1 in rtonly builds (for valid arches)
• ensure no stock build

Signed-off-by: Clark Williams [email protected]