public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
	kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/4] kdevops: add support for A/B testing
Date: Fri, 25 Jul 2025 18:16:48 -0700	[thread overview]
Message-ID: <20250726011653.2622672-1-mcgrof@kernel.org> (raw)

Leverage KDEVOPS_BASELINE_AND_DEV to enable A/B testing.
When     KDEVOPS_BASELINE_AND_DEV is enabled we can let the user
now pick and choose different kernel tree and ref tag for A and B.

With all the automation we have ongoing, this will let us compare
performance / features / enhancements. With automation in place, it
also means we can get bots do easily do testing for us for random
inquiries in the future.

The first patch can go in with this or it can go with Daniel's work.
The CLAUDE.md changes are lessons learned for Claude code based on
cleaning up after it. One minor ansible warning is included as well.

Luis Chamberlain (4):
  Makefile: add make style for style checking
  CLAUDE.md: new workflow guide for hosts and nodes
  gen_nodes/gen_hosts: avoid usage of fs_config_path on task names
  bootlinux: add support for A/B kernel testing

 CLAUDE.md                                   | 689 ++++++++++++++++++++
 Makefile                                    |   5 +
 PROMPTS.md                                  |  48 ++
 docs/kdevops-make-linux.md                  | 158 +++++
 kdevops-ci                                  |   1 +
 playbooks/roles/bootlinux/defaults/main.yml |  12 +
 playbooks/roles/bootlinux/tasks/main.yml    |  99 ++-
 playbooks/roles/gen_hosts/tasks/main.yml    |   4 +-
 playbooks/roles/gen_nodes/tasks/main.yml    |   2 +-
 scripts/check_commit_format.py              |  85 +++
 scripts/detect_whitespace_issues.py         | 109 ++++
 scripts/fix_whitespace_issues.py            | 137 ++++
 scripts/infer_last_stable_kernel.sh         |  35 +
 workflows/linux/Kconfig                     | 116 +++-
 workflows/linux/Makefile                    |  39 ++
 15 files changed, 1529 insertions(+), 10 deletions(-)
 create mode 160000 kdevops-ci
 create mode 100755 scripts/check_commit_format.py
 create mode 100755 scripts/detect_whitespace_issues.py
 create mode 100755 scripts/fix_whitespace_issues.py
 create mode 100755 scripts/infer_last_stable_kernel.sh

-- 
2.47.2


             reply	other threads:[~2025-07-26  1:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-26  1:16 Luis Chamberlain [this message]
2025-07-26  1:16 ` [PATCH 1/4] Makefile: add make style for style checking Luis Chamberlain
2025-07-26  1:16 ` [PATCH 2/4] CLAUDE.md: new workflow guide for hosts and nodes Luis Chamberlain
2025-07-26  1:16 ` [PATCH 3/4] gen_nodes/gen_hosts: avoid usage of fs_config_path on task names Luis Chamberlain
2025-07-26  1:16 ` [PATCH 4/4] bootlinux: add support for A/B kernel testing Luis Chamberlain
2025-07-26 18:00   ` Chuck Lever
2025-07-26 20:21     ` Luis Chamberlain
2025-07-26 21:37       ` Luis Chamberlain
2025-07-26 22:46       ` Luis Chamberlain
2025-07-26 23:16         ` Chuck Lever
2025-07-26 23:34           ` Luis Chamberlain
2025-07-26 23:35       ` Chuck Lever
2025-07-27  0:06         ` Luis Chamberlain

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=20250726011653.2622672-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@kruces.com \
    --cc=kdevops@lists.linux.dev \
    /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