aboutsummaryrefslogtreecommitdiffstats
path: root/jobs
AgeCommit message (Collapse)AuthorFilesLines
2021-05-17some more git.sysmocom.de https (+path) changes due to gitea migrationHarald Welte1-1/+1
Change-Id: Ie1599b356932ffa83d70e08b96179b7ca4909b14
2021-05-04jobs/ttcn3: add TTCN3-centos-*-2021q1Oliver Smith1-0/+30
Depends: docker-playground Icf1e3f1928658ff3d82190c4176252cf3590a1f5 Related: SYS#5370 Change-Id: I2ec731d7d6d31c06b8feccbc7620128ebb034299
2021-04-29OBS: require PROJ environment variable to be setOliver Smith1-1/+2
Uploading to network:osmocom:* should only be done when these scripts are running in the Osmocom jenkins. Remove the default and require users of the script to explicitly set PROJ. Related: SYS#5370 Change-Id: If49ce217e77716b63dfde9139e869672a54b66a2
2021-04-25add jenkins jobs for TTCN3 tests of osmo-pcap-clientHarald Welte1-0/+7
Change-Id: I4283c3f578a9baccddc693d4b09043502212a8e5
2021-04-25release-tarballs: Don't rely on system-installed 'known_hosts'Harald Welte1-1/+7
We should do like the various contrib/jenkins.sh scripts and bring our own known_hosts file to deploy to ftp.osmocom.org. This fixes deploying after merging If0d57ef9edc4d6b3fdf435e44573a15d64245b6a recently. Change-Id: Ia598739f820c8b00c33382afbbe88bf2638241dc
2021-04-22osmocom-release-tarballs: Switch from rita -> ftp.osmocom.orgHarald Welte1-1/+1
We should use service-aliases and not the primary host name, as that makes migration between machines hard. Change-Id: If0d57ef9edc4d6b3fdf435e44573a15d64245b6a
2021-04-13disable gbproxy-latest TTCN3 tests for the time being.Harald Welte1-6/+7
The latest tagged libosmocore misses several important features and it is currently not economic to maintain a test suite for the older NS dialect. Change-Id: I3c87ec54c86ecbfe0c358178b4d8dafd613db584
2021-03-31jobs: Add TTCN3 test job for osmo-ns-dummy master "sns" and "fr"Harald Welte1-0/+7
Change-Id: I1e7bb5a00b91ca3cb33750c9f2035125b797b45c Related: SYS#5396
2021-03-30Add TTCN3 test job for osmo-ns-dummy masterHarald Welte1-0/+3
Related: OS#5396 Change-Id: I3442c1fb826385a847f3965306bc48249474176a
2021-03-15jobs: Add OGT open5gs build jobsPau Espin Pedrol3-1/+8
Change-Id: Ib7786d077017b24825d575b6801cb7c7f08ea832
2021-03-12jobs/osmocom-release-tarballs: adjust containersOliver Smith1-1/+3
Build debian-stretch-obs-latest instead of debian-stretch-build, before building debian-stretch-build-dist. Depends: docker-playground I2cf6ed732e55b8f0e63bd8fc040749bd16676d0f Change-Id: I4189ab1bf483f0a31ffdb35af0d42fe2e9a72a90
2021-03-10jobs/ttcn3: add myself to e-mail recipientsOliver Smith2-2/+2
Change-Id: I415816035fe959f91984c3496a8d1aecfc5c3885
2021-03-10jobs/ttcn3-testsuites: kernel: keep workspaceOliver Smith1-0/+2
Don't wipe the workspace of kernel tests. Cloning the kernel sources takes a great amount of time and traffic, so we want to keep them around. Change-Id: Ifbf6ea127011d8c9fc5c08b584d99ea0220c3e1a
2021-03-09jobs/master,gerrit: run osmo-{bts,trx} in dockerOliver Smith2-14/+16
Build both of them in docker, like most other projects. Depends: docker-playground Ieec31fd6a2034c4430be81afd1d370816cd577d5 Related: OS#5055 Change-Id: Ifc11730192b852d3760a31a561efc61a1a853674
2021-03-08jobs/*: update references to rpi4 nodesOliver Smith4-16/+20
Use the new label that matches all three rpi4 nodes in master-builds and gerrit-verifications (so the builds can run on any of them). Use the names of the three nodes in update-osmo-*-on-slaves, so all of them get updated. Related: https://jenkins.osmocom.org/jenkins/label/rpi4-raspbian10/ Related: OS#5055 Change-Id: I5b2af801baeb510e7784d6bcd7cabfda4962af0c
2021-03-04jobs/ttcn3: add TTCN3-centos-*-latestOliver Smith1-5/+53
Depends: docker-playground I274b31d4903df07e99fd434af25bdb72991f6923 Related: OS#5049 Change-Id: I9a29fddc93789cd285d85445830cc26016af9768
2021-03-04jobs/ttcn3-testsuites-kernel-git: remove wrong commentOliver Smith1-1/+0
Here, the job names are not the same as the directory names of docker-playground.git Related: OS#3208 Change-Id: Idbcb7267ce38cbdc2df5631df404f908487f827b
2021-03-04jobs/ttcn3-testsuites-kernel-git: make userfriendlyOliver Smith1-8/+14
Change the description of the job, to make it easier to use for somebody not familiar with the Osmocom stack / the testsuites. Move the BRANCH parameter to the bottom, as it is not relevant for kernel developers who want to test their kernel, and adjust the description. Related: OS#3208 Change-Id: I0968ae716c8e3f32db6f589b28d6066d95ad85ea
2021-03-04jobs/ttcn3-testsuites-kernel-git: add OSMOCOM_VERSIONOliver Smith1-1/+11
Let the user choose whether to run against osmo-ggsn latest or master. I chose the name "OSMOCOM_VERSION" for the variable to make this easier to use for people not familiar with the Osmocom stack / the test infrastructure, as suggested in the related issue. Related: OS#3208 Change-Id: Ifaf8ed6502b469ade670c3f436670480d27becd6
2021-03-04jobs/ttcn3-testsuites-kernel-git: trigger manuallyOliver Smith1-4/+2
Related: OS#3208 Change-Id: I3a141372b0648a03b35b2b274949a001851f6ca6
2021-03-04jobs/ttcn3: add new ggsn-test-kernel-latest jobsOliver Smith1-0/+36
Add new nightly jobs, as requested in OS#3208: - ttcn3-ggsn-test-kernel-latest-torvalds - ttcn3-ggsn-test-kernel-latest-net-next Note that they are in ttcn3-testsuites.yml and not testsuites-kernel-git.yml, because the KERNEL_URL etc. parameters are not configurable. These new jobs are supposed to run every night with the same hardcoded git repositories, the other job from testsuites-kernel-git.yml is for manual runs with a freely configurable kernel URL. Depends: docker-playground Iaef87c3418b8e6f1e427b2abd9d40e9e28dc63e9 Related: OS#3208 Change-Id: I6918b953b64b0d81805fd02b1a8469a8db20f938
2021-03-02jobs/ttcn3: split *-kernel-git to own fileOliver Smith2-38/+116
Move ttcn3-ggsn-test-kernel-git into its own file, so the parameters that are only relevant for cloning a kernel from git, do not show up in all other TTCN-3 jenkins jobs. Related: OS#3208 Change-Id: Iafbe6139db47c2918dc1fd7c3bacf38da326d9c8
2021-03-02ttcn3-testsuites: Enable TTCN3 for osmo-smlc-latestHarald Welte1-6/+6
now that osmo-smlc is part of network:osmocom:latest, test it both on debian9 + centos8 Change-Id: I023e47531b24f540645186f3cbf89f5025b7b48b
2021-03-02jobs/ttcn3: describe ttcn3-ggsn-test-kernel-*Oliver Smith1-9/+16
Related: OS#1943 Change-Id: If9975e8df46d51ef66c7a9faaf11fc0449f32f34
2021-03-02jobs/ttcn3: disable failing jobsOliver Smith1-0/+2
As decided in the meeting, disable jobs in the config instead of manually disabling them in the web UI. Change-Id: I11e9504cace39d7377e993537c6746fe154b3f12
2021-03-01jobs/ttcn3: add KERNEL_* parametersOliver Smith1-2/+22
Make it possible to run the jenkins job with a different kernel repository, by exposing KERNEL_URL, KERNEL_REMOTE_NAME and KERNEL_BRANCH. Related: OS#3208 Change-Id: I5d4202a67a24d9c15a5b211fa29ce9d5b5a9d9c1
2021-03-01jobs/ttcn3: rename ttcn3-ggsn-test-kernel-net-nextOliver Smith1-3/+3
Change the name of the job to ttcn3-ggsn-test-kernel-git. A follow-up patch will add parameters to the jenkins job to specify a different repository than net-next, therefore the generic name makes more sense. Related: OS#3208 Change-Id: I409f49f88f0a75c782dd3c90c5051e8287644138
2021-02-26jobs/ttcn3: add osmo-ggsn kernel testsOliver Smith1-1/+32
Run osmo-ggsn ttcn3 tests against the gtp kernel module from the debian kernel and from HEAD of the linux netdev/net-next git repository. Depends: docker-playground I1f337af1e2de6db05b22636bc31a535404235559 Related: OS#3208 Change-Id: I4c496af78820d95549da22c1271bafe911f7eefb
2021-02-26jobs/ttcn3: tweak shell cmdOliver Smith1-8/+14
Move 'cd' and './jenkins.sh' commands towards the end, so they are not repeated in the case block of each pattern. This is in preparation for the ggsn kernel mod test, which will need new patterns. Related: OS#3208 Change-Id: I0fac24b961b1abb09317144ec2f65d4e21eb70c2
2021-02-26jobs/ttcn3: add wipe_workspace to job templateOliver Smith1-0/+2
Prepare for the ggsn kernel module test, where we don't want to wipe the workspace with the cloned linux git tree. Related: OS#3208 Change-Id: Ic5843513c376d2b78be8ab90b21a747d31a827f1
2021-02-23ttcn3-testsuites: Enable testing of osmo-cbc "latest"Harald Welte1-3/+3
We do have "latest" packages, so we can start testing it Change-Id: I9f8fb03d9a02da7174bc1aa2aef412e7dbc0724e
2021-02-22jobs: Fix names of commented-out SMLC test containersHarald Welte1-2/+2
This was a copy-+paste introduced in Ib1f374974444cdd5d829c4e57153137ecd9149f1 Change-Id: I8b315e2df34ccd9db78173ee6e83b4d8ec85e8bf
2021-02-22ttcn3-testsuites: Add osmo-cbc testsHarald Welte1-0/+9
Change-Id: I29eb72570d1f80c0f690878597c03afad5bb7b10
2021-02-11jobs/registry-triggers: add for osmo-ttcn3-hacksOliver Smith1-0/+32
Trigger registry-rebuild-upload-titan on changes in osmo-ttcn3-hacks.git. Write registry-triggers.yml with a job template, so we could add more triggers from git repos -> registry easily if needed in the future. Related: OS#5017 Change-Id: Ib6a27be6351ce821c7023a1f75a82b1ade2ffa49
2021-02-11jobs/registry-rebuild-upload-titan: new jobOliver Smith1-0/+37
Trigger for this job will be added in follow-up patch. Related: OS#5017 Change-Id: I2c4b264abf760894edb0788054fd987f9346b6ec
2021-02-11jobs/registry-update-base-images: fix typosOliver Smith1-2/+2
Change-Id: Ifc6c85e638818113182802841c3e0e4a7e6cfda8
2021-02-11jobs/master-builds: libosmocore: add triggersOliver Smith1-0/+2
Add missing triggers for osmo-gbproxy, osmo-trx. Related: OS#4992 Change-Id: I1bc590cc9560b1780cccd99f7ca86700bd9a6ad9
2021-02-10repo-install-test: add label for relevant nodesOliver Smith1-0/+4
Add the slave axis again, so the jobs aren't stuck forever. I had assumed that without the axis, it would run on any node, but that's not how it works. Add a label for this job, with several nodes attached, like we do it for TTCN-3, master-builds, gerrit-verifications etc. Related: https://jenkins.osmocom.org/jenkins/label/repo-install-test/ Related: OS#4567 Fixes: fcf669 ("repo-install-test: run on all build slaves again") Change-Id: I276ab47f76a0f4db542ca99825ebb019236b4d27
2021-02-08repo-install-test: run on all build slaves againOliver Smith1-5/+0
It was not possible to reproduce the weird rpm errors on admin2-deb9build, which had lead to limiting the build slaves to build2-deb9build-ansible. Enable building on all again. Closes: OS#4567 Change-Id: I82ef1f0c581de8ee826adedd9ecde6b4adaa36ba
2021-02-03master + gerrit jenkins jobs: Add osmo-gbproxyHarald Welte2-0/+2
osmo-gbproxy is moving to its own reporitory Change-Id: Id29c83bdcd9b626bb7920738c8b1f945ef7f3671
2021-01-25repo-install-test: add 'debian10'Oliver Smith1-2/+4
Related: OS#4969 Depends: docker-playground I7addb30aa3f8564dcbdc3f6cf2e2e0cfdf4dd02d Change-Id: If0fc12464b571dc42b33f2a077c77ea6e5120b8d
2021-01-25repo-install-test: rename 'debian' to 'debian9'Oliver Smith1-1/+1
Related: OS#4969 Depends: docker-playground I2ea18997019ebaa013c258996f5131386bcd6426 Change-Id: Iaa2202cca4072b4dc0309e011aba6cb33ed5b8aa
2021-01-21jobs/repo-install-test: run a few hours laterOliver Smith1-1/+1
Give OBS more time to build the repository, before verifying that we can install all packages from the repository. Apparently, OBS publishes the repository in WIP state, before all packages for a distribution have been built. This leads to problems in the "nightly" and "next" repositories. In contrary to "latest", we do not bump soname versions when doing ABI changes, so we require the user to have all installed Osmocom packages built from the same timestamp. With recent changes in the OBS scripts, we enforce this by having all packages built from the same timestamp depend on the exact version of a dummy package with that timestamp as version. The repo-install-test installs all packages from the binary repository, and so it fails, as it should, if the repository is in an inconsistent state with some packages built today and some packages built yesterday. Related: OS#4733 Change-Id: I8df9b449d6213b5dca6fd9bf5c06b5c96d468f66
2021-01-21Cosmetic: jobs/obs: update repo-install-test nameOliver Smith1-1/+1
Change-Id: Ic5712173ec79d286fb3591364636a38f6af74503
2021-01-13jobs: remove duplicate docker_runOliver Smith2-55/+0
docker_run was duplicated for osmo-e1-hardware and no2bootloader, so the '-e PATH' line could be removed from the global docker_run. It was overriding the PATH, which then did not contain the path to the compiler toolchain anymore. This workaround is not needed anymore since de5aa17d6 ('jobs: don't overwrite PATH in "docker run"'). Related: OS#4911 Change-Id: I97a4add17d9fa1bd28ab0ceb054b9a8d948b6f86
2021-01-13jobs: update OSMO_GSM_MANUALS_DIROliver Smith2-9/+9
Use new location inside / outside docker, where the repository was cloned already. So it does not need to be cloned during the job. Roll out: make sure that the docker images are already built! (or let me merge it) Related: OS#4912 Depends: docker-playground Id402e0ea372b5ca8a6c8f6f5beb190544c888207 Change-Id: Ibe91a613162687589e006cba99193606fb8a3eb9
2021-01-13jobs/osmo-gsm-manuals-trigger: new jobOliver Smith1-0/+37
On change, roll out osmo-gsm-manuals to relevant build environments. Related: OS#4912 Change-Id: I104525826068b016b5e06ea52567da4d7beaf7a4
2021-01-12jobs: add missing OSMO_GSM_MANUALS_DIROliver Smith2-4/+21
Add the variable to projects that don't use docker at all or overwrite docker_run instead of using the global variable that has OSMO_GSM_MANUALS_DIR defined. Related: OS#4912 Change-Id: I65102655b4b3e907a0b0de8026f8f9af76281f90
2021-01-12jobs: don't overwrite PATH in "docker run"Oliver Smith3-5/+2
Don't mount $HOME/bin to /build_bin, and don't overwrite PATH to include /build_bin anymore. This isn't needed because the scripts are installed to /usr/local/bin inside the docker images now. Depends: docker-playground I0820f13cd740f7d4a8999d279cef6ae293a67d81 Related: OS#4911 Change-Id: I45bd7ea56849dab839a98cfd52806f7cd288094e
2021-01-12osmo-build-dep.sh: don't build osmo-gsm-manualsOliver Smith2-0/+2
Save time by only cloning the repository, and not running autoreconf -fi, ./configure, make and make install. Especially the tests during make took up significant time, that slowed every project depending on osmo-gsm-manuals down while being built through master-builds or gerrit-verifications jobs. Set OSMO_GSM_MANUALS_DIR to the clone location. This is an interim measure, I'll submit more patches soon that remove the 'osmo-build-dep.sh osmo-gsm-manuals' calls from all projects. Change-Id: I5238cf3f93ded97ed2b44d27868123a646e122dc Related: OS#4912
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-09 18:40:51 +0000