aboutsummaryrefslogtreecommitdiffstats
path: root/jobs/gerrit-binpkgs.yml
AgeCommit message (Collapse)AuthorFilesLines
2024-04-25OBS: move gerrit-binpkgs logic to separate scriptOliver Smith1-21/+3
As I'm preparing slides for a OsmoDevCon talk, I'm realizing that it is quite cumbersome for users to build debian packages from Osmocom git repositories (the same way gerrit does it, to reproduce errors locally). Move the logic from the gerrit-binpkgs job to a separate script that can be run from an Osmocom git repository, will figure out the repository name from there and only needs the target distribution as argument. Usage example: $ git clone https://gitea.osmocom.org/osmocom/osmo-ci $ cd libosmocore $ ../osmo-ci/scripts/obs/gerrit_binpkgs.sh debian:12 # or debian:11, debian:10, almalinux:8 Change-Id: I100d8dfc0c58bdafe7efb0fa4108031ce10398a5
2023-12-04jobs: fix undefined parameter log warningsOliver Smith1-20/+1
Adjust all jobs in the gerrit verifications pipeline to use the same parameters from a new include file, to prevent undefined parameter warnings in the log. Fixes: OS#6261 Change-Id: Iadc5cd8996eb4ed86634ceb35829a3e9239e598d
2023-07-31jobs/gerrit-binpkgs: don't hardcode distrosOliver Smith1-23/+15
Make it possible to set a list of distributions to check in gerrit-verifications.yml instead of only having one boolean for testing two hardcoded rpm and deb distributions. Change-Id: I59487e3dc2f55057de1b6a322f088fff0d18654c
2023-04-03jobs/gerrit: increase num-to-keep to 1000Oliver Smith1-1/+1
Increase the logs to keep for gerrit related builds, as they may exceed the previous limit of 120 within a day. All these jobs don't save build artifacts, so they should not cause a noticable size increase. This is a much more careful version of 719ff976 ("jobs: tweak build-discarder values"), which had been reverted in a052c13c. The big problem with the previous patch was that it increased the number of jobs to keep even for jobs that had build artifacts, and so the required storage exploded. Related: OS#5980 Change-Id: I1a4604d7a5093349aee0122e74914b06045c78b8
2023-04-03jobs: remove artifacts-days/num-to-keep: -1Oliver Smith1-2/+0
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-03-28Revert "jobs: tweak build-discarder values"Harald Welte1-0/+3
This reverts commit 719ff9760808acb1fe944f4c496c356c7dc07c91. 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-07jobs: tweak build-discarder valuesOliver Smith1-3/+0
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
2022-12-06jobs: retire osmocom-gerrit-debian* labelsOliver Smith1-1/+1
Let the gerrit-binpkgs and gerrit-pipeline-result jobs use the "osmocom-gerrit" label. Having the -debian10/11 label previously was useful to make sure this doesn't run on an ancient python version that fails on f-strings. But since the debian9 builders were retired, this is not needed anymore. These are the only jobs that used these, so now the labels in the README can be simplified (following patch). Related: OS#5793 Change-Id: Ieee95d25e036dcd4869d89b10c281179024672e7
2022-11-10jobs/gerrit-binpkgs: don't use multiple-scm pluginOliver Smith1-8/+10
Change the default branch from origin/master to master, as the git clone command expects just the branch name without a remote name. Related: OS#5763 Change-Id: Ia5a17c6d25bf811a992ab495a2531ae613cb144f
2022-10-11jobs/gerrit-binpkgs: new job for deb, rpm packagesOliver Smith1-0/+118
Build deb and rpm packages for each patch submitted to gerrit for the projects in the list. Example: https://gerrit.osmocom.org/c/osmo-bsc-nat/+/29492 Related: OS#2385 Change-Id: I7ca8869c2e9f2e7c74a360933be12b5c2b47c2fc