aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-04-09osmo-clean-workspace.sh: make more robust against broken git clonesNeels Hofmeyr1-4/+25
Change-Id: Ifa70fd75468b3e21b5c9327ea28bc7a4c8cb549d
2018-04-09osmo-clean-workspace.sh: cosmetic: no need to clean -e depsNeels Hofmeyr1-1/+2
git clean always excludes git clone subdirs; furthermore, even if I supply a dir as -e, the contents of that dir still get cleaned out. So it is useless to pass -e on the commandline. Drop it. Change-Id: I2b59cc9c9adf88a2663469b22cfeffbd66b5bf2e
2018-04-06jenkins: add job osmo-gsm-tester_gerritAlexander Couzens2-0/+64
The job verifies the gerrit patchset. Change-Id: If661675528059bc8a95d39a6489a5a9381f52677
2018-04-06jenkins: add osmo-gsm-tester_run-{prod,rnd}Alexander Couzens3-0/+146
Both jobs doing the actual test run on the prod or rnd tester. Change-Id: Ic1c4babc547f48402b0bcfaf38e2734e87e565f0
2018-04-06jenkins: add job osmo-gsm-tester_build-trigger-allAlexander Couzens1-0/+29
osmo-gsm-tester_build-trigger-all triggers a new build of all osmo-gsm-tester build jobs. Change-Id: I8dcf2a6fa2991cb73b4807f8a10d251f3dca77dd
2018-04-06jenkins: add osmo-gsm-tester-build jobsAlexander Couzens1-0/+99
The build jobs building all osmocom components which will be used by the osmo-gsm-tester. A .tgz archive will be used as artefact which is copied later by the osmo-gsm-tester test run. Change-Id: Ic49c94e9e6639e43f6ae14b868bc826af3ce2085
2018-04-05ansible jenkins-slave: only setup ttcn3_slave on debian stretchAlexander Couzens1-1/+1
Change-Id: Iaf043008890da94098986468e1fd3d9578810206
2018-04-05ansible: install eclipse-titanAlexander Couzens1-0/+17
Change-Id: I354271b7c573484b7f538a5a4bb29753a950d5f9
2018-04-05jobs/update-osmo*: add new nodes to the update jobsAlexander Couzens2-2/+2
Change-Id: Ib103b3343d582f7a78f0c4cec00c94078a078584
2018-04-05ansible: hosts: add host2-deb8build-ansible host2-deb9build-ansibleAlexander Couzens1-0/+3
Change-Id: If0a21f24483b2c1c6ea56e366c5858eee50f17e1
2018-04-05ansible: create a new group coverity-slaves to choose the target of coverityAlexander Couzens2-1/+9
Change-Id: I8b09ca50db938c5c7087a74e5d2575412a916ff6
2018-04-05ansible: hosts: use inventory with ansible_host to have more readable ↵Alexander Couzens1-8/+4
ansible output As long they don't have a dns entry, use the ansible_host variable Change-Id: I0888e9b66cd1077dcdada97fb5ee2d56def516e3
2018-04-05ansible: hosts: add build2-deb8build-ansible build2-deb9build-ansible slavesAlexander Couzens1-0/+4
Change-Id: Iede01ab10f0a9582b3a3a9a3ebbbc684b94a3c0a
2018-04-05ansible: osmocom-jenkins-slave: don't install recommend packagesAlexander Couzens1-0/+1
libuhd-dev would recommend uhd-host which seems not be installable on debian jessie in an lxc. However we should have already listed all explicit dependencies and shouldn't need anything else Change-Id: I6859b8180916a8e172d32030da06ba6fa27d5c45
2018-04-04jobs/master: optimize trigger chainNeels Hofmeyr1-12/+75
Avoid as many multiple triggers as still ensure all dependent projects are rebuilt correctly. Keep the full trigger list as comment, and illustrate in a comment at libosmocore how the chain is intended to work. Change-Id: Iea2cf25b3872045778f11a985a1c417f37067cd9
2018-04-02scripts: osmo-deps.sh: Allow building against tagsPau Espin Pedrol1-1/+6
In case we provide a tag, origin/$tag doesn't resolve correctly, we must use $tag. Same happens probably if we want to build against a specific commit hash. Change-Id: Ica50080c8b3e20686fe6f47a2b61718ef4a66d95
2018-04-02ansible: Add docbook5-xml to jenkins build slavesHarald Welte1-0/+1
Change-Id: Ic0a33a87a61c9cdd1ca60a023bbf2920d04fefcd Related: OS#3072
2018-03-29jobs/master-builds: move all builds to debian 9 slaveNeels Hofmeyr1-4/+2
Change-Id: I6f025c642d5ae57cdda9d7b34bbaeb82ca119354
2018-03-29jobs/master-builds: drop useless 'node' fieldNeels Hofmeyr1-2/+0
The slaves to build on are determined by the slave_axis, the node parameter has no useful effect. Change-Id: I029de2a46f22a1b1dc977bce71137eb78b826157
2018-03-27ansible: jenkins-slave: setup ttcn3 repositoryAlexander Couzens3-0/+22
Change-Id: I3aa1bf52f6fcae129278dab7081ea5cfc97d0759
2018-03-17jobs: osmo-trx: Disable temporarily ARM buildsPau Espin Pedrol2-2/+6
proot crashes with current jenkins node setup, which means we cannot use it to run ARM based axis. proot bug is already reported upstream in: https://github.com/proot-me/PRoot/issues/134 Related: OS#3061 Change-Id: I9bc48349c78f395b3842bc5caaf6e948fb4c299e
2018-03-17ansible/roles/osmocom-jenkins-slave/tasks/main.yml: Fix alpha sortingHarald Welte1-2/+2
Change-Id: Ifdcdcd76edf791d66cbd44daa0797c61ab5d83f0
2018-03-17Add laforge@gnumonks.org to all build failure notificationsHarald Welte1-1/+1
Change-Id: I989075eb0cd930d42daa36d9d8501592141c0310
2018-03-16add ansible playbooksAlexander Couzens34-0/+843
Introduce playbooks to do: - setup-jenkins-slave - setup a usualy or special jenkins-slave - setup-gsm-tester - setup the gsm-tester Change-Id: I7007a4e6c38f73843390ec2b3b91133aff21e36a
2018-03-07osmocom-latest-packages.sh: Catch latest tags outside master branchPau Espin Pedrol1-1/+1
Some projects, like osmo-trx, may have tags created in a non-master branch. Let's catch those too. Tested with several osmocom repositories. The ones showing different behaviour are osmo-trx (expected) and other repositories which have wrong or no tags and are anyway not used since there's no OBS build for them. Old cmdline is left of ==, new is right: artwork: ( == ) asn1c: ( == ) docker-playground: (debian-jessie-buildslave-0.1.0 == ) layer1-api: (superfemto_v3.8.1 == ) libasn1c: (0.9.28 == 0.9.28) libgtpnl: (1.1.0 == 1.1.0) libosmo-abis: (0.4.0 == 0.4.0) libosmocore: (0.10.2 == 0.10.2) libosmo-netif: (0.1.1 == 0.1.1) libosmo-sccp: (0.8.1 == 0.8.1) libsmpp34: (1.12.0 == 1.12.0) meta-telephony: ( == ) mncc-python: ( == ) octphy-2g-headers: (OCTSDR-OPENBSC-02.09.00-B1121 == ) openbsc: (1.0.0 == 1.0.0) osmo-bsc: (1.1.2 == 1.1.2) osmo-bts: (0.7.0 == 0.7.0) osmo-ci: ( == ) osmocom-bb: (osmocon_v0.0.0 == ) osmo-ggsn: (1.1.0 == 1.1.0) osmo-gsm-manuals: ( == v1) osmo-gsm-tester: ( == 0.1) osmo-gsm-tester-conf: ( == ) osmo-gsm-tester-sysmocom: ( == ) osmo-hlr: (0.1.0 == 0.1.0) osmo-iuh: (0.2.0 == 0.2.0) osmo-mgw: (1.2.0 == 1.2.0) osmo-msc: (1.1.2 == 1.1.2) osmo-pcu: (0.4.0 == 0.4.0) osmo-python-tests: ( == ) osmo-sgsn: (1.2.0 == 1.2.0) osmo-sip-connector: (1.1.0 == 1.1.0) osmo-trx: (0.2.0 == 0.3.0) pysim: ( == ) python-smpplib: ( == ) Change-Id: I3b521a194f0ae9fdfa358423e66f30c1316c23e8
2018-02-27osmo-clean-workspace: fix force checkout of a subdirectoryAlexander Couzens1-2/+2
Instead of the subdirectory, the main repository was forced checked out. Change-Id: If23e89872edf48dc5b751b3c069faf585bd6a3ef
2018-02-25jenkins: gerrit-builds: replace the label linux_amd64_debian8/9 -> ↵Alexander Couzens2-4/+6
osmocom-gerrit-debian8/9 Introduce more precise labels to allow more flexibility when extending the jenkins setup. The linux_amd64_debian8 or linux_amd64_debian9 is used across all build jobs which make it hard to add new nodes which might only support one group of jobs. Change-Id: I900b7b50b33cc95e127ca78d2a47f59d32a6dfee
2018-02-25jenkins: master-builds: replace the label linux_amd64_debian8/9 -> ↵Alexander Couzens2-4/+12
osmocom-master-debian8/9 Introduce more precise labels to allow more flexibility when extending the jenkins setup. The linux_amd64_debian8 or linux_amd64_debian9 is used across all build jobs which make it hard to add new nodes which might only support one group of jobs. Change-Id: I0fa3d3f81ab01e2488fe07601740f42eb54b6d9c
2018-02-25jenkins: add node admin2-deb8build to the update jobsAlexander Couzens2-2/+2
Change-Id: I6b703b9f27865b146f20bea953fe3d6500a88166
2018-02-25jenkins: add node admin2-deb9build to the update jobsAlexander Couzens2-2/+2
Change-Id: Ie3803a46ee192dc72823291004ee20f4bdbe0126
2018-02-15ttcn3 gerrit verification: Use 'make deps-update' targetHarald Welte1-1/+1
In osmo-ttcn3-hacks Idc165425b45872d2eb958a662d03e69aaf60669d we introduced the new 'deps-update' Makefile target to properly update all 'deps' repositories without removing them. Let's use it. Change-Id: Iabc54182d1d30ef26e4f72fb9db52fd25a6c9800
2018-02-10jobs: add Coverity Upload JobAlexander Couzens1-0/+35
Change-Id: I852b42a698a4568b51e993bb5e86efeed6afdb32
2018-02-09master-builds: Add missing dependencies / triggersHarald Welte1-9/+21
There were a lot of downstream triggers that we were missing. I manually reviewed the debian/control files and used that to update the trigger lists for all jobs in master-builds.yml. Change-Id: I12057c9bb389041ef3bcabd1c335a0fa8c358092
2018-02-06jobs/README.adoc: explain the usage of API Tokens instead of passwordsAlexander Couzens1-0/+3
Change-Id: Ie96288913aae2fe97fa11266ffa9ed098044ccfd
2018-01-22jenkins: fix jobs templateMax2-0/+4
The sequential parameter was silently skipped because it was absent from the project template. Fix this for both master- and gerrit- jobs. Change-Id: I0bc28695f4f270bc7b1cc4bcd5d4d43ede6172f3
2018-01-22cosmetic: remove wrapper scriptMax2-40/+38
The jenkins.sh is just a tiny wrapper around coverity_Osmocom.sh - let's remove this unnecessary indirection and move the code directly to jenkins.sh Change-Id: Iead3b8f39327f1d0dd80e12a9d38563c35701993
2018-01-22cosmetic: remove unused functionMax1-4/+0
Change-Id: Ie3885237cea2afbe5e8c0f89d2280284bb4d9150
2018-01-22Coverity: specify sysmoBTS L1 headers explicitlyMax1-1/+1
Fix upload by specifying L1 headers location properly. Fixes: OS#2845 Change-Id: Iba55922295cb2a258f90c5345f592d7d5f34ac51
2018-01-21libosmocore: use dispatcher scriptMax2-14/+2
Get rid of job name comparison because it depends and exact build server name and hence is highly fragile. Use dispatcher script the same way we do in osmo-bts. N. B: this requires I2955e866bce4f000a53369bd601a346c36c82468 in libosmocore. Change-Id: I76dfc11a05007ae5c6e0554fe8132695b67cccaa
2018-01-21jobs: Add {master,gerrit}-libusrpHarald Welte2-0/+2
Change-Id: I2b208455b7bd008fb25322280894c100e51f2227
2018-01-19gerrit-verifications.yml: osmo-sgsn: Remove duplicated concurrent attributePau Espin Pedrol1-1/+0
Change-Id: I808c46c2f4488fd577bb1c23cd13c5b73519265b
2018-01-19jobs: master: also trigger once per dayNeels Hofmeyr1-0/+1
Recently we had changes to osmo-ci, and I noticed that although some master builds were broken by that, the builds were still showing success -- of twenty days ago. Run each master build at least once a day to indicate odd side effect failure sooner. Change-Id: I126de2bab3db22cb693b0fa665f6579de9238fdf
2018-01-17Don't run OsmoPCU tests in parallelMax2-0/+2
The vty and ctrl tests are enabled by default and are run on hard-coded ports. This causes some builds to fail when run in parallel. Change-Id: I23d5b75825a667e4f043d16a12b841cd8f01af5e
2018-01-17Install pip tool into containersMax3-3/+3
The pip(2|3) tool is the officially recommended tool to deal with Python packages [1] with much greater flexibility compared to invoking setup.py directly. As a preparation step for using it to install osmo-python-tests let's add it to container images. [1] https://packaging.python.org/guides/tool-recommendations/ Change-Id: If2702c71cd268ca688e9ecc264f8cd1257c27899
2018-01-17Fix missing OsmoPCU master buildMax1-6/+6
Similar to Idac6e53b1e0addbcb5b6c99b8051e1e0ad26bc5b fix the master branch builds. Change-Id: Icdd53a7cb037324a568e8eab529716e030e00583
2018-01-15jobs: osmo-trx: Set slave_axis to use only debian9Pau Espin Pedrol2-2/+2
Debian 8 contains quite old qemu and proot packages which have some issues running the chroot infrastructure set up in osmo-trx's jenkins.sh. Change-Id: I24665880fff5a5b918bb6ffaf1e7bb51ae860b0b
2018-01-15docker: rebuild: if building fails, try a --no-cache buildYour Name1-1/+3
Building a docker image depending on a debian upstream has the problem that an intermediate build result will depend on an APT package archive that is probable to become outdated. It's necessary to do an 'apt-get update' regularly to get the newest package archives and be able to install new packages. We never know which 'apt-get install' steps we might be editing, so we'd have to add an 'apt-get update' before each, or use an ADD line to find out whether the package archive has changed, before each and every apt-get install step. We're likely to miss those in the future, and it would be a large, complex change. Instead, try to build the docker image with --no-cache in case a cached build has failed. This should fetch the most recent debian upstream with a proper archive. Fixes the current problem that the rebuild_osmocom_jenkins_image.sh is stuck on various build slaves, should trigger a --no-cache build on each slave. Change-Id: I37110287dabd53d3537d94ecd74cf513396971b3
2018-01-15docker: debian: install stow IN THE RIGHT dockerfileNeels Hofmeyr1-1/+1
Recent change I8f5012419495a656912b7b71e4f76ce102c6b63a adds use of stow in osmo-build-dep.sh, hence our jenkins build processes now require the 'stow' dependency. Add 'stow' to our debian docker images, used for various builds (those that invoke 'docker' in the jobs/master-builds.yml and jobs/gerrit-verifications.yml to produce concurrent builds). A recent commit made this change in the Dockerfile.deb8_* dockerfiles, in the assumption that the jenkins one would depend on that, which is actually not the case. Instead, add stow in the dockerfile that is actually used in the jenkins jobs. (It is not harmful to still keep the added dependency in the other two dockerfiles.) Change-Id: If97176f4aea66c42a6820f14ceb4b91369841ca0
2018-01-15docker: debian: install stow, now used in various buildsNeels Hofmeyr2-2/+2
Recent change I8f5012419495a656912b7b71e4f76ce102c6b63a adds use of stow in osmo-build-dep.sh, hence our jenkins build processes now require the 'stow' dependency. Add 'stow' to our debian docker images, used for various builds (those that invoke 'docker' in the jobs/master-builds.yml and jobs/gerrit-verifications.yml to produce concurrent builds). Note: the Dockerfile.deb8_i386 doesn't seem to be used, currently. Add stow there anyway. Change-Id: I7a44ba5ed130a3311460185507f76151c6daa7f1
2018-01-15README: also hint at /n/home/dub8/.config/jenkins_job_builder/jenkins_jobs.iniNeels Hofmeyr1-3/+6
Change-Id: I8bb6792ab061edd3d688e387fa69cd8637617dee
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-24 14:23:49 +0000