Lines Matching +full:check +full:- +full:ci +full:- +full:script
4 Occasionally, the Gitlab CI needs a Linux Kernel update to enable new kernel
5 features, device drivers, bug fixes etc to CI jobs.
6 Kernel uprevs in Gitlab CI are relatively simple, but prone to lots of
7 side-effects since many devices from different platforms are involved in the
11 -----------------
13 The Linux Kernel used in the Gitlab CI is stored at the following repository:
14 https://gitlab.freedesktop.org/gfx-ci/linux
20 So, one should base the kernel uprev from the last tag used in the Mesa CI,
21 please refer to `.gitlab-ci/container/gitlab-ci.yml` `KERNEL_URL` variable.
22 Every tag has a standard naming: `vX.YZ-for-mesa-ci-<commit_short_SHA>`, which
25 :code:`git tag vX.YZ-for-mesa-ci-$(git rev-parse --short HEAD)`
28 ---------------
30 When Mesa CI generates a new rootfs image, the Linux Kernel is built based on
31 the script located at `.gitlab-ci/container/build-kernel.sh`.
36 When a Kernel uprev happens, it is worth compiling and cross-compiling the
38 resulting Kconfig is a merge between *Mesa CI Kconfig* and *Linux tree
39 defconfig* made via `merge_config.sh` script located at Linux Kernel tree.
44 +------------+--------------------------------------------+-------------------------------------+
45 | Platform | Mesa CI Kconfig location | Linux tree defconfig |
47 | arm | .gitlab-ci/container/arm.config | arch/arm/configs/multi_v7_defconfig |
48 +------------+--------------------------------------------+-------------------------------------+
49 | arm64 | .gitlab-ci/container/arm64.config | arch/arm64/configs/defconfig |
50 +------------+--------------------------------------------+-------------------------------------+
51 | x86-64 | .gitlab-ci/container/x86_64.config | arch/x86/configs/x86_64_defconfig |
52 +------------+--------------------------------------------+-------------------------------------+
55 -------------------
59 :code:`.gitlab-ci/container/gitlab-ci.yml` tag
61 - **KERNEL_URL** for the location of the new kernel
63 :code:`.gitlab-ci/image-tags.yml` tags
65 - **KERNEL_ROOTFS_TAG** to rebuild rootfs with the new kernel
66 - **DEBIAN_X86_TEST_GL_TAG** to ensure that the new rootfs is being used by the Gitlab x86 jobs
69 -------------------
74 …h a new development branch to `Kernel repository`_ based on the latest kernel tag used in Gitlab CI
75 5. Hack `build-kernel.sh` script to clone kernel from your development branch
77 7. Run the entire CI pipeline, all the automatic jobs should be green. If some job is red or taking…
82 1. Push a new tag to Mesa CI `Kernel repository`_
83 2. Update KERNEL_URL `debian/x86_test-gl` job definition
87 ---------------
93 it is suggested that one runs the entire CI pipeline to check if the update affected the manual CI …
95 Step-by-step
102 5. Compare the job results. If a CI job turned red on your uprev branch, it means that the kernel u…
104 Bare-metal custom kernels
107 Some CI jobs have support to plug in a custom kernel by simply changing a variable.
111 `BM_KERNEL`. If one puts a gz-compressed kernel URL there, the job will use that
112 kernel to boot the freedreno bare-metal devices. The same works for `BM_DTB` in