summaryrefslogtreecommitdiffstats
path: root/jobs
AgeCommit message (Collapse)AuthorFilesLines
2020-04-17jenkins: add osmo-uecups to gerrit+masterHarald Welte2-0/+2
Change-Id: I3ca141edcd61ae4126fa28f6560c99a1f568dec7
2020-04-10jobs: osmo-gsm-tester: Update path to sysmocom's specific setupPau Espin Pedrol5-18/+18
Since osmo-gsm-tester.git I364e0859c0851b9167907a4d948b659a0f6a19fb the example/ directory has been renamed to sysmocom/ Change-Id: I4c7516d2eb9636d37391a81dc9d484c0c04d7191
2020-03-16 job: Update master and gerrit osmo-pcu jobs to also build on ARM platformPau Espin Pedrol2-11/+15
Related: OS#4301 Change-Id: I8109cc9a71e6c14304ed6463f9b073ef3f4f3c2a
2020-03-12ansible: Use osmo-gsm-tester docker image in jenkins job osmo-gsm-tester_virtualPau Espin Pedrol1-1/+1
Let's use the osmo-gsm-tester docker image based on the debian-stretch-jenkins instead of the later directly, since the former has all osmo-gsm-tester required dependencies. Change-Id: I256eeed82eef0969d93dc015e043b0417f56f52c
2020-03-03jobs: update-osmo-python-on-slaves: osmo-python not required in simtester nodePau Espin Pedrol1-1/+0
Change-Id: Ia3728cf9296eab8db49274e4da64249e497726d1
2020-03-03jobs: jenkins simtest node is named simtesterPau Espin Pedrol2-2/+2
simtest node doesn't exist, it's called simtester. Fixes: 3935743127633815b068cd57469775722c3710e3 Change-Id: Id703a85298b163e7e95bb89f6a69ab51e29effb4
2020-02-26add build2-deb10build-ansible build slaveHarald Welte2-0/+2
This is our first Debian 10 build slave Change-Id: Iae80c5f73781d14ffbf124a476894d4631c83dc7
2020-02-26jobs: add 'simtest' to the list of to be updated slavesVadim Yanitskiy2-0/+2
Change-Id: I0cc6188aab10ecb8b862710d272c411e47a21f61
2020-02-26jobs: Run update-osmo-{ci,python}-on-slaves on rpi4-deb9build-ansiblePau Espin Pedrol2-0/+2
Change-Id: I96067ffc0061a85bcc46569b1bf38eade3b8d995
2020-02-26job: master-buids.yml: Drop specific scm and poll branch for master-osmo-pcuPau Espin Pedrol1-5/+0
Change-Id: I12f0c5c83786feba0aef74143fab3a836e83cd9d
2020-02-26job: Update master and gerrit osmo-bts jobs to also build on ARM platformPau Espin Pedrol2-19/+23
Related: OS#4301 Change-Id: I72e228ff1a126f6c41c5fd6a530de85e177a0d21
2020-02-26job: Update master and gerrit osmo-trx jobs to also build on ARM platformPau Espin Pedrol2-8/+10
Related: OS#4301 Change-Id: I0049ab35b5106d5af8474903e203f66b044ff5ca
2020-01-29jobs: Introduce osmo-gsm-tester_build-srsltePau Espin Pedrol3-0/+7
Change-Id: I08a59c6065ca4fb6fbbed5b12e73abf4024f1dcb
2020-01-17ttcn3-testsuites.yml: Add job for ttcn3-sccp-testPau Espin Pedrol1-0/+4
Only for nightly, not latest, since example/sccp_demo_user is not installed by autotools and debian packages, so only in nightly where we build from source we are able to copy it to docker image manually. Related: OS#4343 Change-Id: Ia0a68d74215bdc1bc6319241d60f858312fa14e9
2020-01-17gerrit-verifications: fix erlang/osmo_ss7 nameOliver Smith1-5/+5
Fixes: aadc60f4037dcf9529a30d362648b0f0849825c2 ("jobs/gerrit-verifications.yml: add erlang repos") Related: OS#4345 Change-Id: Id78f7e62e12c7595329ef8a265e522f27a087604
2020-01-17gerrit-verification: fix erlang cmdOliver Smith1-4/+3
Jenkins job builder only does one pass of variable substitution. Replace the cmd_erlang variable with its contents, so the jobs don't fail with: [osmocom-gerrit-debian9] $ /bin/sh -xe /tmp/jenkins7189809471369692535.sh + {docker_run} {docker_img_erlang} /build/contrib/jenkins.sh /tmp/jenkins7189809471369692535.sh: 2: /tmp/jenkins7189809471369692535.sh: {docker_run}: not found Fixes: aadc60f4037dcf9529a30d362648b0f0849825c2 ("jobs/gerrit-verifications.yml: add erlang repos") Related: OS#4345 Change-Id: I6e121c79ecf872a7058de3a6dc0a940fa8091f68
2020-01-17osmocom-release-tarballs: publish with rsyncOliver Smith1-0/+10
Related: OS#3870 Change-Id: I5f88ae0c483ed03c42c47d1cd207ac2722cfa083
2020-01-15jobs/gerrit-verifications.yml: add erlang reposOliver Smith1-0/+18
Run contrib/jenkins.sh in erlang repositories, that were recently updated (osmo_gsup, osmo_dia2gsup, osmo_ss7). Depends: docker-playground Ia3eaec6090c9652549b2850de74ee21730374bbd Related: OS#4345 Change-Id: I05d152de6b7a04dee935d79b9987c511351eca95
2020-01-15docker: move to docker-playground.gitOliver Smith4-3/+28
Instead of building "osmocom:deb9_amd64" from this repository, build "$USER/debian-stretch-jenkins" from docker-playground.git (same Dockerfile). Adjust all jobs to use the new image name. Add a new "update-osmo-ci-on-slaves-dp" jenkins job, which triggers the existing "update-osmo-ci-on-slaves" job whenever docker-playground.git changes. Replace docker/rebuild_osmocom_jenkins_image.sh with scripts/osmo-ci-docker-rebuild.sh, so we can get rid of the docker dir. I thought about dropping the script completely, and directly writing the two lines into contrib/jenkins.sh. But I kept the extra script for convenience, when testing locally. Related: OS#4345 Depends: docker-playground I125ae8a6bcabbd1f485028c79b0abacda0622c3a Change-Id: I30a61aebcadef5536e74edd35e1c75ef77a2da9f
2020-01-14gerrit-verifications: introduce "gerrit_url" varOliver Smith1-2/+3
Prepare for erlang repositories, which will use this variable. Related: OS#4345 Change-Id: Ia91764797745b48ae832cfbc16976e561b288a50
2020-01-08jobs/update-osmo-ci-on-slaves: origin/master onlyOliver Smith1-0/+2
Don't run, when different branches were pushed. Change-Id: I2cf55391066b60cf6a594f528ed0eaf59a886391
2019-12-04master-builds: add osmo-{cbc,e1d,e1-recorder}Harald Welte1-0/+3
Change-Id: Idfede8e9e79019b67b9aff4881d5cea97514aeba
2019-12-04add gerrit-verifications for osmo-e1-recorder and osmo-cbcHarald Welte1-0/+2
Change-Id: I1df28b4e7a7cbcf9151cd57a77001d88f1875415
2019-12-04Cosmetic: gerrit/master jobs: link to wikiOliver Smith2-1/+4
Place a link to the wiki page, that now documents all available environment variables. Related: OS#4243 Change-Id: I770360b671c64369cf6cdb4fb4222921cc6af58e
2019-12-02jobs/master-builds.yml: fix osmo-fl2kOliver Smith1-11/+1
Don't use the old "osmocom:amd64" image. Remove the entire cmd line, so it uses the default docker command with the default docker image "osmocom:deb9_amd64". Also remove concurrent: true, because that default nowadays too. Related: OS#3203 Change-Id: I93db12d3652f26db059e0ede52d2b2fdd3e89d34
2019-12-01jobs/master-builds.yml: add osmo-fl2kOliver Smith1-0/+11
Related: OS#3203 Depends: https://lists.osmocom.org/pipermail/osmocom-sdr/2019-July/001951.html Change-Id: Iac411a5d5e312b8db0b5388f58571141fb2f32df
2019-12-01add '--publish' to osmo-asf4-dfu and osmo-ccid-firmware buildsHarald Welte1-1/+6
Change-Id: Ie45b9fcabc35f6fd9aff33af0f0587c8ccd88ebd
2019-11-23WIP: coverity: Make sure curl is installed, as our coverity upload job needs itHarald Welte1-0/+10
This is untested. I'm on the train and have very limited understanding of Ansible Change-Id: I9918b89971bf6c2e200f1d96d993d5fbd6741b71
2019-10-24jobs: Introduce ttcn3-stp-test(-latest) jenkins jobPau Espin Pedrol1-0/+4
Change-Id: I7a82e1fa82cd28433cdb7a9128c7ab3da6cabf47
2019-10-18gerrit, master builds: default to concurrent: trueOliver Smith2-24/+12
Now that almost everything runs in docker, we don't need to worry about problems with running VTY/CTRL tests in parallel for these projects. Related: OS#3726 Change-Id: I5fdf759faf47ec7e4f9cb2657bd004585a667add
2019-10-18gerrit, master builds: build almost all in dockerOliver Smith2-42/+34
Instead of building some projects in docker, and some directly on the build slave, build almost all of them in docker with few exceptions, and make building in docker the default. This has several advantages: * build environment of master builds and gerrit verifications is the same, therefore the same build won't pass in gerrit and then fail in master * all build environments are volatile * no more conflicts while running VTY/CTRL tests * fix osmo-python-tests gerrit review versions being installed to /usr/local of build slave (see previous commit message) Projects that still do not get built in docker: * openggsn: depends on libgtpnl, but does not build it in jenkins.sh * osmo-bts: l1headers, various SDKs not installed in the docker image * osmo-trx: LimeSuite is not in the docker image (and just installing the debian package does not work) * osmo-ttcn3-hacks: TTCN-3 not installed in docker image * pysim: needs to access real sim cards attached to the host * sysmo-usim-tool: needs to access real sim cards attached to the host Related: OS#3726, OS#3598 Change-Id: If4b7d2f9ffbc7e92699732d97a8f5829a88c5b35
2019-10-15jobs/master-builds.yml: Set node for master axis jobPau Espin Pedrol1-1/+1
Otherwise the master job managing the axis can be run on any node, something which is not desirable. For instance, right now job master-osmo-ggsn is run on osmo-gsm-tester-rnd which is currently unable to fetch some git repositories. Let's avoid running master tests on unintended nodes. Change-Id: I62abb3c490588adc4c0e13c761de44d442f8cefe
2019-09-24gerrit, master builds: use stretch, not jessieOliver Smith2-2/+6
Debian jessie (8) is EOL already, so switch to stretch (9). This is required to build all Osmocom projects in docker, because at least libosmocore fails to build with the old image (tests won't build with GCC-4.9.x from jessie unless -Werror is disabled). Do not build the jessie image anymore, and update the shared dockerfile. Remove everything jessie specific, and make it work with stretch by installing asciidoc-dblatex. Otherwise we get this error when building manuals: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl Add '--cap-add SYS_PTRACE' argument to the docker run command, because otherwise the address sanitizer isn't working anymore with stretch (which makes the OsmoPCU tests fail). I've tried to split this patch up into multiple ones, but since there is no asciidoc-dblatex package in jessie, we must add the dependency and switch the image at the same time. Related: OS#3726 Change-Id: I61fe93863d5367e3b9c01ab4726bb95bd16d891d
2019-09-23gerrit, master builds: add docker_{run,img} varsOliver Smith2-173/+57
Move the common "docker run" invocation and image name into one place, so it is not duplicated over and over. This prepares for changing the image and building all Osmocom projects in docker (follow up patches). Related: OS#3726 Change-Id: If529e6a93bb2227230981ee22f2c75bd0f1f4518
2019-09-19gerrit, master builds: concurrent OsmoPCU buildsOliver Smith2-3/+33
Re-enable concurrent builds for OsmoPCU, and run all builds in docker. This should prevent previous problems with VTY/CTRL test collisions, which lead to the concurrent builds being disabled in I23d5b75825a667e4f043d16a12b841cd8f01af5e. Related: OS#4204 Change-Id: I4f90a601e41dca18a6fcbab56bdf5663167d2353
2019-09-13jenkins-jobs: Add ttcn3-remsim-test for {master,latest]Harald Welte1-0/+4
Change-Id: Ib4e3f3f0153c38765868cfd2014cd56cd47c2c79
2019-08-23gerrit-verifications: fix osmo-bts cmdOliver Smith1-1/+1
Fixes: 932b0037506130692bc8a1aa1edd95d5f54efd11 ("gerrit, master builds: use ASCIIDOC_WARNINGS_CHECK") Change-Id: Ia17d6a14ede93bae715fb67826b074ab91f87749
2019-08-21gerrit, master builds: use ASCIIDOC_WARNINGS_CHECKOliver Smith2-16/+26
The asciidoc warnings check fails the build if asciidoc prints a warning while building the documentation. We had this enabled by default, but since OBS uses various asciidoc versions, we could get unexpected build failures (different asciidoc versions print different warnings). Now that it is disabled by default, explicitly enable it for jenkins again. Related: OS#4140 Depends: Iac993a0d1b17205397a1f1ef1a7bd3f9df739e36 (osmo-gsm-manuals) Change-Id: I8775d45b4dc1a5a46e2ba042fc7ee7d9f10f18cc
2019-07-30master-builds: Publish osmo-hnbgw documentationDaniel Willmann2-1/+3
Requires: Ic7437daeab0b07d16fd71ca3881cb31bab7b1925 (osmo-iuh) Change-Id: Ia1be4ef79a1089d7af582acb63eb3afa5a60f4f3
2019-07-26jobs: upload to OBS before debian-install testOliver Smith2-2/+2
Make sure that we don't test yesterday's packages. Adjust timers to run the OBS job around 1 o'clock, and the debian-install test around 4 o'clock. Use the H (hash) symbol for minute to spread the load. Change-Id: I503058018172d50e9585d4804dfec1b4ece7644a
2019-07-23osmocom-debian-install.yml: add BRANCH variableOliver Smith1-1/+7
Allow changing the branch in the jenkins UI when starting the build. We already have this in other jobs, and it is very useful to test changes. Change-Id: Ice4662551625b3c96ca105629a934a0a081db2e4
2019-07-23osmocom-debian-install.yml: update descriptionOliver Smith1-1/+5
Replace "Generated by job-builder" with a proper description. The job builder automatically adds "<!-- Managed by Jenkins Job Builder -->" to the description (which is visible when editing the job), so we don't need to mention it in the description at all. Related: OS#3369 Change-Id: I17d2e9e0ac7fe77fb0306724a1f1e15641d76854
2019-07-11gerrit-verifications: add libtelnetOliver Smith1-0/+1
Related: OS#3047 Change-Id: Iafffd9d938ee310bb729b3e2a0a4d80870d4b3b5
2019-07-02jobs: add osmocom-release-tarballs.ymlOliver Smith1-0/+54
Related: OS#3870 Depends: I991fe41a1f55ccd6a66815ec3d7f239850397d9a (docker-playground) Change-Id: I994da5c27f9198e5bcf2d567dd473f9ed078d9c0
2019-05-23jobs/osmocom-obs.yml: set default git branchOliver Smith1-0/+7
I was quite surprised, that the job used "osmith/pdfs-in-doc-subpackage" instead of "master" today [1]. Fix this randomness by adding a branch parameter that defaults to "master". Interestingly, we have to set the default branch to "refs/remotes/origin/master". When using "*/master" (like we do in other jobs), Jenkins would still chose my branch over "origin/master", even though mine does not have "master" in the name. I have also tried "chosing-strategy: 'default'", in case it was using the gerrit strategy for some reason (like in [2]), and setting 'refspec:', but both did not have any effect. [1] https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_nightly/98/ [2] https://issues.jenkins-ci.org/browse/JENKINS-26981 Change-Id: I6d1f0e70d5c82ffd551d00ffdf2712cbfaec16cf
2019-05-11Add osmo-e1d to gerrit-verifications.ymlHarald Welte1-0/+1
Change-Id: I78cfd6052aebbe8cfa215928906f18f8afe3c06a
2019-04-30OBS: add links to job descriptionOliver Smith1-1/+7
Add the links that the obsolete Osmocom_nightly_packages job has, before we remove it. Also link to the binary packages wiki page. Change-Id: Idbc7ccd0156d9c3eb6d30059384686849a36f49f
2019-04-17jobs: use "cmd: |", not "# keep first line ..."Oliver Smith3-41/+23
Adjust README.adoc to mention "cmd: |" instead of the workaround and replace this: cmd: > # keep first line with less indent to preserve newlines docker run ... With that: cmd: | docker run ... Change-Id: I65a06acb76e5d693aa187f9ac38970b73e7fead6
2019-03-28Add bscnat tests to jenkinsDaniel Willmann1-0/+4
This requires Change-ID I800ebe0f33cf7c86eea65d2e186c6af12fee6db7 from osmo-ttcn3-hacks. Fixes: OS#3179 Change-Id: Idee5a986e4cda8db601982ac3f2662bc20fe3f5f
2019-03-28ttcn3: Order tests by time triggeredDaniel Willmann1-15/+15
We had some load issues with many things running at once on jenkins. This will at least make it easier from having colliding ttcn3 jobs. I also changed ttcn3-sip-test to run at 7:30 instead of 7:00 where ttcn3-bts-test runs. Change-Id: I65f346a3fae2811c8314c26d4a5b3a528b8101f9