Commit Graph

11 Commits

Author SHA1 Message Date
Oliver Smith f71fceff65 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-13 14:55:23 +02:00
Harald Welte 910a04d39c DAHDI gerrit verification job diversification
* we never really wanted to build against fixed tags but branches, i.e.
  "the latest tag within a given stable series", so switch from a fixed
  tag like "v5.10" in torvalds/linux.git to "linux-5.10.y" in stable/linux.git

* we also want to build against 6.1.y, as that is what upcoming Debian
  bookworm will ship

Change-Id: I60aa61cb5020c9ce50126b048a0fa546a535236f
2023-06-06 16:29:40 +02:00
Oliver Smith b126b77e81 jobs: remove artifacts-days/num-to-keep: -1
Remove the "artifact-days-to-keep: -1" and "artifact-num-to-keep: -1"
lines, as they don't have an effect. -1 is the default value, which
means "infinite" and causes the value from "days-to-keep" /
"num-to-keep" to get used instead.

This patch re-applies part of 719ff976 ("jobs: tweak build-discarder
values"), which had been reverted in a052c13c.

Related: https://jenkins-job-builder.readthedocs.io/en/latest/properties.html#properties.build-discarder
Related: OS#5980
Change-Id: Ic073643634e1814147d765dd7e8f3f02e81effc3
2023-04-03 10:47:54 +02:00
Harald Welte a052c13c12 Revert "jobs: tweak build-discarder values"
This reverts commit 719ff97608.

The disk consumption of jenkins has grown by almost 500GB
since we merged this patch.  Clearly this is not expected, and we'd
have ran out of disk space in a few weeks.

I personally think the current allocation of 1.5TB of disk space to
jenkins should be more than sufficient; we just need to manage it
better.

Closes: OS#5980
Change-Id: I6b744a8b84a3e1255a8d51f73d1721ccfd028ac1
2023-03-28 13:35:33 +02:00
Oliver Smith 719ff97608 jobs: tweak build-discarder values
Remove num-to-keep from most jobs, as this leads to keeping the build
logs for a much shorter timeline than desired. For example the
gerrit-binpkgs-deb job that runs for most projects when pushing patches
to jenkins reaches the 120 limit in less than 24h - and so when clicking
the link on a failed build from yesterday it is already deleted.

Instead just keep the logs for the last 30 days, no matter how many were
submitted on one day. Storing logs doesn't take up much space.

Remove the artifact-days-to-keep and artifact-num-to-keep lines, as they
don't have an effect. For jobs that do have artifacts, the actual value
is min(days-to-keep,artifact-days-to-keep) and same with num-to-keep.

While at it, increase the ttcn3-testsuites build-discarder to 120 days
as this means more data will show up in the test result analyzer at
which we look frequently.

Change-Id: Iec5c22c7fcf6c1fd2db71611045f15dc6580ed86
2023-03-07 12:05:29 +01:00
Oliver Smith 5f0876d674 jobs: don't limit to debian9
Related: OS#5793
Change-Id: Idcbbf766928964c4896aef7c6687ea7003203427
2022-11-30 17:46:57 +01:00
Oliver Smith 28ace174fa jobs/gerrit…-dahdi: don't use multiple scms plugin
Don't use the deprecated plugin. Let jenkins clone the big linux
repository and clone the code from gerrit in the shell section of the
script. Since we can't directly clone $GERRIT_REFSPEC, create an empty
git repository and fetch it.

Related: OS#5763
Change-Id: I52314f55e7e55382b4e8fcd63d3aba306b401447
2022-11-10 16:45:09 +01:00
Oliver Smith 191ecd07cf jobs/gerrit-verifications*: drop unsupported args
Fix warnings when updating the job with Jenkins Job Builder:
  WARNING:jenkins_jobs.modules.triggers:Gerrit Trigger property 'no-name-and-email' is deprecated
  WARNING:jenkins_jobs.modules.triggers:Gerrit Trigger property 'trigger-for-unreviewed-patches' is not supported in this plugin version

Related: OS#2385
Change-Id: I6a0057738955bc2507cb5d8c4d48edf652c3529f
2022-10-13 10:51:55 +02:00
Harald Welte 032c0de4b8 dahdi-linux: Add gerrit build verification against master
Now that master-dahdi-linux-master is passing, we should verify any
future patches also against master.

Change-Id: I86cfd7e868dcaeeb6c6dbc6f08046a70b4582cc7
2022-04-24 19:48:47 +02:00
Harald Welte 5b933d8aea dahdi: use buster, not stretch
stretch has too old gcc which doesn't support -Wno-format-truncation
which is used in dahdi-linux since 2018.

Related: OS#5407
Change-Id: I4fca722e67b2c649dea4f9799d277cd568bcc493
2022-04-24 18:20:58 +02:00
Oliver Smith b3cef938c9 jobs/gerrit-verifications-dahdi.yml: new file
Add gerrit verifications for the out-of-tree dahdi-linux kernel module.
Put this in a separate file (not gerrit-verifications.yml), because:
* not only gerrit git repo gets cloned, but also linux.git, and caching
  needs to be done properly for it
* so we can have one separate job per linux version that gets tested

Test v4.19 and v5.10 for now, as suggested in the issue.

Related: OS#5407
Depends: docker-playground Id72d19ad08681cd7cb3194de2226292f19e96df5
Change-Id: I65c7663a6b8045796536a727e4adf5554f16b2a9
2022-02-04 14:40:17 +01:00