T6674: remove all references to Jenkins

CONTRIBUTING.md

@@ -40,7 +40,7 @@ task first. Once there is an entry in Phabricator, you should reference its id
 in your commit message, as shown below:
 
 * `ddclient: T1030: auto create runtime directories`
-* `Jenkins: add current Git commit ID to build description`
+* `keepalived: T1234: do not autostart service, will be done by CLI`
 
 If there is no [Phabricator](https://vyos.dev) reference in the
 commits of your pull request, we have to ask you to amend the commit message.

README.md

@@ -40,7 +40,6 @@ There are several directories with their own purpose:
  * `scripts/`  Scripts that are used for the build process
  * `tools/`    Scripts that are used for maintainer's tasks automation and other
                purposes, but not during ISO build process
- * `vars/`     Jenkins Pipeline library for reusable functions
 
 # Building VyOS
 

docker/Dockerfile

@@ -204,7 +204,6 @@ RUN wget https://salsa.debian.org/klausenbusk-guest/debootstrap/commit/a9a603b17
     sudo dpkg -i ../debootstrap*.deb
 
 # Packages needed for Linux Kernel
-# gnupg2 is required by Jenkins for the TAR verification
 # cmake required by accel-ppp
 RUN apt-get update && apt-get install -y \
       cmake \

scripts/package-build/linux-kernel/README.md

@@ -5,9 +5,9 @@
 
 # About
 
-VyOS runs on a custom Linux Kernel (which is 4.19) at the time of this writing.
-This repository holds a Jenkins Pipeline which is used to build the Custom
-Kernel (x86_64/amd64 at the moment) and all required out-of tree modules.
+VyOS runs on a custom Linux Kernel (which is 6.6) at the time of this writing.
+This repository holds build scripts that are used to build the Custom Kernel
+(x86_64/amd64 at the moment) and all required out-of tree modules.
 
 VyOS does not utilize the build in Intel Kernel drivers for its NICs as those
 Kernels sometimes lack features e.g. configurable receive-side-scaling queues.
@@ -33,9 +33,3 @@ VyOS utilizes several Out-of-Tree modules (e.g. WireGuard, Accel-PPP and Intel
 network interface card drivers). Module source code is retrieved from the
 upstream repository and - when needed - patched so it can be build using this
 pipeline.
-
-In the past VyOS maintainers had a fork of the Linux Kernel, WireGuard and
-Accel-PPP. This is fine but increases maintenance effort. By utilizing vanilla
-repositories upgrading to new versions is very easy - only the branch/commit/tag
-used when cloning the repository via [Jenkinsfile](Jenkinsfile) needs to be
-adjusted.