osmo-ci/jobs/gerrit-verifications-dahdi.yml

104 lines
2.9 KiB
YAML
Raw Permalink Normal View History

- project:
name: gerrit-dahdi-linux-stable
type: stable
repo: 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git'
linux-ver:
- "linux-4.19.y"
- "linux-5.10.y"
- "linux-6.1.y"
jobs:
- 'gerrit-dahdi-linux-{type}-{linux-ver}'
- project:
name: gerrit-dahdi-linux-torvalds
type: torvalds
repo: 'https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git'
linux-ver:
- "master"
jobs:
- 'gerrit-dahdi-linux-{type}-{linux-ver}'
- job-template:
name: 'gerrit-dahdi-linux-{type}-{linux-ver}'
project-type: freestyle
node: osmocom-gerrit
concurrent: true
retry-count: 0 # scm checkout
properties:
- build-discarder:
days-to-keep: 30
num-to-keep: 120
description: |
Pending gerrit code reviews of
<a href="https://gerrit.osmocom.org/#/q/status:open+project:dahdi-linux">dahdi-linux</a>
built against linux {linux-ver}
(<a href="https://osmocom.org/issues/5407">OS#5407</a>)
<br/><br/>
<b>Auto-generated using Jenkins Job Builder. DO NOT EDIT MANUALLY!</b>
scm:
# Let jenkins clone the big linux repository and keep it between builds
# (wipe-workspace is false). Clone dahdi-linux with code from gerrit in
# the shell part below.
- git:
basedir: 'linux'
url: '{repo}'
branches:
- '{linux-ver}'
refspec: '{linux-ver}'
shallow-clone: true
wipe-workspace: false
clean:
before: true
triggers:
- gerrit:
trigger-on:
- patchset-created-event:
exclude-drafts: true
exclude-no-code-change: true
projects:
- project-compare-type: 'PLAIN'
project-pattern: 'dahdi-linux'
branches:
- branch-compare-type: 'ANT'
branch-pattern: '**'
skip-vote:
successful: false
failed: false
unstable: false
notbuilt: false
silent: false
escape-quotes: false
server-name: gerrit.osmocom.org
builders:
- shell: |
rm -rf dahdi-linux
git init dahdi-linux
cd dahdi-linux
git config advice.detachedHead false
git fetch \
--depth=1 \
https://gerrit.osmocom.org/dahdi-linux \
"$GERRIT_REFSPEC"
git checkout FETCH_HEAD
cd ..
docker run \
--rm=true \
-e "KSRC=/linux" \
-v "$PWD/dahdi-linux:/build" \
-v "$PWD/linux:/linux" \
jobs: master/gerrit: use debian bookworm (12) Upgrade from debian 11 for master and debian 10 for gerrit verifications to using debian 12 for both. Previously we intentionally built against the older debian 10 version to ensure that our programs still build there. However it is easier to maintain the docker containers if we just use the most recent debian version for both and it makes the build environment more consistent - if a patch passes in gerrit verifications, we expect it to pass in master builds as well. And the other way around, I can just run CI of all master jobs when developing a change and assume that if they pass, gerrit verifications will run as well. As long as we provide binary packages in OBS for debian 11, 10, ... we will still notice if a build breaks on an older debian release. I think this is good enough given that it will probably not happen that often, but if we decide that we really want to ensure it still builds on older distros at gerrit-verification time then the more suitable place to add this would be in the deb-build verification test. It is more maintainable there, because the dependencies just get installed from the debian/control file, no need to add all of them to a docker container beforehand. The new container is debian-bookworm-build, see the docker-playground commit for reasoning why it is not debian-bookworm-jenkins. Related: OS#6057 Depends: docker-playground I49aaf62b5b97775f923453611df3b91354a640a0 Change-Id: I079e55a1325083714c8d39f922b2563e843fc0bc
2023-07-12 14:53:00 +00:00
"$USER/debian-bookworm-build" \
timeout 10m su build -c /build/contrib/jenkins.sh
publishers:
- warnings:
console-log-parsers:
- 'GNU C Compiler 4 (gcc)'
resolve-relative-paths: true
# vim: expandtab tabstop=2 shiftwidth=2