aboutsummaryrefslogtreecommitdiffstats
path: root/jobs
AgeCommit message (Collapse)AuthorFilesLines
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
2019-03-27Avoid '/' in jenkins matrix labelsDaniel Willmann1-2/+2
The script already deals with this for osmo-bts by using the version_prefix variable Change-Id: I3102fc607718ca42634273e24e6ff303dc28483f
2019-03-27Also build oc2g support for osmo-pcuDaniel Willmann1-2/+3
Needs gerrit change I7cd89a549c9463e81893ca7dd925299f728e4453 in osmo-pcu Fixes: SYS#4524 Change-Id: Iebddf8d41538fe1e69435cda7f77bd49c4c14477
2019-03-26jobs: add osmocom-build-tags-against-master.ymlOliver Smith1-0/+43
Run osmocom-build-old-tags-against-master.sh every night in jenkins. Related: OS#3765 Change-Id: I9868a6008f61fb3962279f72d34f67f900425be5
2019-03-20jobs: add osmocom-list-commits.ymlOliver Smith1-0/+44
Related: OS#3840 Change-Id: I9a65cb750bbe6c278b9f67eb70bdb36759cb775b
2019-03-14ttcn3-testsuites: Split ttcn3-pcu-test-sns from ttcn3-pcu-testHarald Welte1-0/+4
The SNS variant of the tests require the PCU to be started with different config file. Change-Id: I42785b68f136198152ad79072346faccfe4a9424
2019-03-03jenkins: Send build failures to jenkins-notifications mailing listHarald Welte6-2/+20
Change-Id: I5609a0f4b8f176ffa692db732abb4694acaaf927
2019-02-21jobs: osmo-gsm-tester: Add oc2g jobsPau Espin Pedrol3-1/+13
Change-Id: I5ea9b783a2a2017cb134e72087e217a4184184b2
2019-02-21jobs: Introduce a tester using "virtual" testsHolger Hans Peter Freyther1-0/+57
With mobile, virtphy, osmo-bts-virtual we can run e2e tests without the need of any hardware. Create a dedicated job for it. This avoids having to share resources (e.g. lock state/ip allocations) with other builds. Change-Id: I19993b287cc948dbdfba9d375f80a7904f96ff4a
2019-02-20ttcn3-testsuites: Add PCU testsHarald Welte1-0/+4
Change-Id: Ifd8113c8db2b6e84d6e01539a6df031dc6f4ee80 Closes: OS#2890
2019-02-15Fix copy and paste in the script.Holger Hans Peter Freyther1-1/+1
Change-Id: I51d01a8799f09ce7d813a0ef8353a4233d5c8bb5
2019-02-05jobs/osmo-bts: Build osmo-bts-oc2g as wellDaniel Willmann1-3/+4
Build osmo-bts with support for oc2g as well. Uses origin/nrw/oc2g as firmware. Fixes: OS#3745 Change-Id: Iaaeb44b949cf6403601f069800c381fe5eae2f6e
2019-02-04gerrit-verifications: Add osmo-ccid-firmwareHarald Welte1-0/+1
The repository currently doesn't yet have a contrib/jenkins.sh script, so all verifications will fail. This is intentional, as it will force the addition of a related script in the first merged commit. Change-Id: I713d345240dec319ee07d99e9381fc1af6a2d86d
2019-01-28ttcn3: block latest jobs while master is runningOliver Smith1-12/+25
Jenkins job builder does not support string replacing in variables, so the only way to make each ttcn3-foo-test-latest job get blocked by their ttcn3-foo-test counterpart was specifying them each time. Related: OS#3767 Change-Id: I124286d4b996e79a7b77603c7b59473b016c3bd5
2019-01-28ttcn3-bsc-test-sccplite-latest: enable jobOliver Smith1-2/+1
This job does not get stuck anymore since the latest Osmocom release. Change-Id: Ie87aeb52832b4ce0fbec96d2cff9dd04da0c11fc
2019-01-13add osmo-asf4-dfu master and gerrit jobsHarald Welte2-0/+2
Change-Id: I5bc5ca30809af8d8b472a75a9e02c4964761de38
2019-01-12add maintainer email to simtrace projectKévin Redon1-0/+1
Change-Id: Id0a6740749ea1e3d1c06396485744426b0a74f79
2018-12-12master-builds: openbsc: make SSH keys availableOliver Smith1-0/+1
Mount ~/.ssh in openbsc's docker container, just like it is done with all other Osmocom projects that build in docker (see Change-Id Icfff3b6a620de79d1bab7ff6a35309f828581c09 ("master-builds: make SSH keys available in Docker")). Related: OS#3385 Change-Id: Ib31ab4033c1cc71c10a96445e8bcc3b9f02e2a1f
2018-12-12Build verification: manuals for the restOliver Smith2-2/+11
Build manuals for osmocom-bb and openbsc in gerrit-verifications.yml. Build and publish manuals for osmocom-bb, openbsc and osmo-gsm-tester in master-builds.yml. Following recommendations on the ML, building manuals for osmo-gsm-tester was not done with a new job in gerrit-verifications.yml. It will be done with the existing osmo-gsm-tester_gerrit job (which is generated by osmo-gsm-tester-runner.yml). No changes are necessary for that in osmo-ci.git, see I4ebfe12a164f807b63bc897aff44db83fc0705bd ("contrib/jenkins*: build and publish manuals") in osmo-gsm-tester.git. Related: OS#3385 Change-Id: I2845d14b656f11e3a07107b4f16e8d7a0e3c7bbf
2018-12-05jobs/ttcn3-testsuites.yml: add build-discarderOliver Smith1-0/+5
Add the same build discarder as we have in master-builds.yml. This should help with the disk space problems. Change-Id: Ib7f01751ca5f6fb3e29a436982e2891d9cab0488
2018-12-05gerrit-verifications/master-builds: fix errorsOliver Smith2-2/+8
Fix three errors that prevented Jenkins from accepting the new configs from Ie0643b17a6be6e86e281b50d78dd7a6858cf99ee ("gerrit-verifications/master-builds: WITH_MANUALS"): * master-builds: fourth axis needs to be in the template or else the server will throw a 500 error. gerrit-verifications already has four template axes. * gerrit-verifications/osmo-pcu: || at the end of combination_filter * gerrit-verifications/osmo-sip-connector: missing ":" Change-Id: I4ad63a3167e59b0837ffd1576fb7c7cf2958ff32
2018-12-05gerrit-verifications/master-builds: WITH_MANUALSOliver Smith2-35/+92
Add WITH_MANUALS=1 to generate (and publish in case of master-builds) PDF manuals. Jobs with multiple axes generate the manuals only in the fastest axis. Related: OS#3385 Change-Id: Ie0643b17a6be6e86e281b50d78dd7a6858cf99ee
2018-12-04master-builds: use PUBLISH=1 instead of --publishOliver Smith1-12/+16
Pass all inputs to contrib/jenkins.sh as environment variables instead of mixing with commandline arguments. We decided on this method instead of I3cc01dbc57213b6d6cdc9b394a516510d045f1ae ("use jenkins.sh --publish"), to make the contrib/jenkins.sh scripts less confusing. Related: OS#3385 Change-Id: Ifc88af086368ce8eea1ea3a375ba7d5603a5d7e5
2018-12-04master-builds/gerrit: remove redundant GTP="$GTP"Oliver Smith2-3/+3
Variables for axes are already exported as environment variables. Change 'GTP="$GTP" ./contrib/jenkins.sh' to './contrib/jenkins.sh' to avoid confusion when introducing other variables. Change-Id: I9238da3dd3c4461f82dc7c792f886177399be3dc
2018-12-03osmo-mgw: don't try to build with transcodingOliver Smith2-6/+0
Do not build osmo-mgw twice anymore (once with "--enable-mgcp-transcoding" and once with "--disable-mgcp-transcoding"). configure.ac does not know these options. Change-Id: I080cd331caec31c53a43090e6c19d23e31abdec6
2018-12-03master-builds: make SSH keys available in DockerOliver Smith1-0/+4
At runtime, mount the Jenkins host's ~/.ssh folder inside the Docker containers, from which manual PDFs will be published. To my surprise, local testing showed that ssh is looking for the keys in /home/build/.ssh, although the HOME variable inside the image is set to /build, not /home/build. Related: OS#3385 Change-Id: Icfff3b6a620de79d1bab7ff6a35309f828581c09
2018-11-30cosmetic: gerrit-verifications: format docker cmdOliver Smith1-22/+61
Format the docker command lines just like they are formatted in master-builds.yml. Most notably, this puts every environment variable on its own line. This makes it much easier to compare both files side by side. Change-Id: I0adcb028be24c2e05189c15b85811777d6287387
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-23 03:05:31 +0000