[PATCH 7/9] CONTRIBUTING: Switch to new run-tests.sh

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

From: Jan Kiszka <jan.kiszka@siemens.com>

This massively simplifies the way to invoke the testsuite.

It also obsoletes the old ci_setup.sh script, so drop it.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 CONTRIBUTING.md     | 72 ++++++++++-----------------------------------
 scripts/ci_setup.sh | 32 --------------------
 2 files changed, 15 insertions(+), 89 deletions(-)
 delete mode 100755 scripts/ci_setup.sh

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 07621232..71edabde 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -77,63 +77,21 @@ Plan merges to `master` so that both fit the two-week window; short extensions s
 
    * Seemingly unaffected boards still build.
 
-   * It's highly suggested to test your patchset before submitting it to the mailing
-     by launching CI tests scripts. The procedure is described below:
-
-    ```
-    git clone https://github.com/siemens/kas
-    cat > kas.yml <<EOF
-    header:
-      version: 14
-    build_system: isar
-    defaults:
-      repos:
-        patches:
-          repo: isar
-    repos:
-      isar:
-        url: "http://github.com:/ilbers/isar"
-        branch: next
-        layers:
-          meta:
-          meta-isar:
-    EOF
-    kas/kas-container shell --command /work/isar/scripts/ci_setup.sh kas.yml
-    ```
-
-    In kas shell:
-
-    ```
-    cd /work/isar/testsuite
-    avocado run citest.py -t dev --max-parallel-tasks=1
-    ```
-
-    Your git-formatpatches may be listed in the `kas.yml` file as illustrated below:
-
-    ```
-    ...
-    repos:
-      isar:
-        url: "http://github.com:/ilbers/isar"
-        branch: next
-	patches:
-          0001:
-            path: /work/0001-my-contribution-to-isar.patch
-        layers:
-          meta:
-          meta-isar:
-    ```
-
-    Perform the above steps from a clean directory for your CI run to be as close as
-    possible to the environment that our project maintainers will be using. That
-    directory would contain: *.patch isar/ kas/ kas.yml
-
-    Be also mindful of community-provided resources such as deb.debian.org or
-    snapshot.debian.org and consider using a caching proxy in your setup to
-    reduce traffic as much as possible.
-
-    Active developers may request from maintainers an account on isar-build.org
-    to analyze CI logs or to launch their own CI builds there.
+   * It's highly suggested to test your patchset before submitting it to the
+     mailing list by launching CI tests scripts:
+
+     ```
+     scripts/run-tests -T dev
+     ```
+
+     Perform the above steps over the branch that contain your patches.
+
+     Be also mindful of community-provided resources such as deb.debian.org or
+     snapshot.debian.org and consider using a caching proxy in your setup to
+     reduce traffic as much as possible.
+
+     Active developers may request from maintainers an account on isar-build.org
+     to analyze CI logs or to launch their own CI builds there.
 
 4. Structure patches logically, in small increments.
 
diff --git a/scripts/ci_setup.sh b/scripts/ci_setup.sh
deleted file mode 100755
index f373d1c0..00000000
--- a/scripts/ci_setup.sh
+++ /dev/null
@@ -1,32 +0,0 @@
-#!/bin/sh
-# Script to setup a container for CI builds
-#
-# Cedric Hombourger <cedric.hombourger@siemens.com>
-# Copyright (c) Siemens AG, 2025
-# SPDX-License-Identifier: MIT
-
-gpg_key=/etc/apt/trusted.gpg.d/debian-isar.gpg
-[ -f "${gpg_key}" ] || {
-    wget -q http://deb.isar-build.org/debian-isar.key -O- \
-    | gpg --dearmor \
-    | sudo dd of="${gpg_key}"
-}
-
-list=/etc/apt/sources.list.d/10-isar_build.list
-[ -f "${list}" ] || {
-    echo "deb [signed-by=/etc/apt/trusted.gpg.d/debian-isar.gpg] \
-        http://deb.isar-build.org/debian-isar bookworm-isar main" \
-    | sudo tee /etc/apt/sources.list.d/10-isar_build.list
-}
-
-tools="avocado qemu-system-aarch64 qemu-system-arm qemu-system-i386 qemu-system-x86_64"
-need_install=0
-for tool in ${tools}; do
-    which "${tool}" || need_install=1
-done
-[ "${need_install}" = "0" ] || {
-    sudo apt-get update
-    sudo apt-get install -y avocado qemu-system-arm qemu-system-x86
-}
-
-exec /container-entrypoint ${*}
-- 
2.47.3

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/0707415b2a9875c8101e609e215af9f2f20bdb53.1774254639.git.jan.kiszka%40siemens.com.