aboutsummaryrefslogtreecommitdiffstats
path: root/jobs/master-builds.yml
AgeCommit message (Collapse)AuthorFilesLines
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-17jobs: osmo-trx: Disable temporarily ARM buildsPau Espin Pedrol1-1/+3
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-17Add laforge@gnumonks.org to all build failure notificationsHarald Welte1-1/+1
Change-Id: I989075eb0cd930d42daa36d9d8501592141c0310
2018-02-25jenkins: master-builds: replace the label linux_amd64_debian8/9 -> ↵Alexander Couzens1-4/+4
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-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-01-22jenkins: fix jobs templateMax1-0/+2
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-21libosmocore: use dispatcher scriptMax1-7/+1
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 Welte1-0/+1
Change-Id: I2b208455b7bd008fb25322280894c100e51f2227
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 parallelMax1-0/+1
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-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 Pedrol1-1/+1
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-15master-builds.yml: Build osmo-trx with different optimization instruction ↵Pau Espin Pedrol1-0/+3
sets enabled Change-Id: I651e182dfd62ef4b88d013d8b5960ce7e3562ecf
2018-01-15master-builds.yml: osmo-sgsn: Remove duplicated concurrent attributePau Espin Pedrol1-1/+0
Change-Id: I32938d4c1854ce65faa718eccaecb5e3143dbcd0
2018-01-12Notify per email about master branch build failureMax1-0/+3
Change-Id: I0a72d36d777ba582815b2cdef8130ee88c060b54
2017-12-19jobs: master: fix: libosmoabis should trigger osmo-hlrNeels Hofmeyr1-1/+1
Change-Id: I9a122cee4fa98115140e4a34f623958697affed2
2017-12-15jobs: master: osmo-gsm-manuals: use new jenkins.sh, only on OsmoBuild1Neels Hofmeyr1-11/+3
Change-Id: Ida1301a3f83caff400e80c8b46504f98cb0894ab
2017-12-15jobs: cosmetic: readability: docker one-arg-per-lineNeels Hofmeyr1-19/+53
Change-Id: I8b18a5bc54a879002b40b0fc51cd295e82beba4f
2017-12-15jobs: master: adjust triggers to what was found on old jenkins jobsNeels Hofmeyr1-2/+3
Change-Id: Ib59247978ed92b72949260a79628b28754a44484
2017-12-13jobs: master-builds: fix git master branch pollingNeels Hofmeyr1-1/+1
The 'refs/heads/origin/master' somehow caused that git polling would not trigger builds. 'origin/master' was succesful in a manual test, so set all jobs to that. Change-Id: Id033d1bfce6cc9e20fbbf9be462842b9e44bde83
2017-12-09jobs: Fix osmo-ggsn GTP build optionPau Espin Pedrol1-1/+1
As far as I understand, the variable is populated using the name field. In openggsn build it matches, but it doesn't in osmo-ggsn. Change-Id: Ifb1a630b77a8c2f442e26dbef8e608882e8f9a71
2017-12-09jobs: master: drop legacy openggsn (now is osmo-ggsn, also present)Neels Hofmeyr1-5/+0
Change-Id: I219a988f94b465ac8bb77319735aedbe49707c16
2017-12-09jobs: master: drop unused axis a4Neels Hofmeyr1-6/+0
Change-Id: I4b9db4077eacca649c679333e24b2eb7338a96e6
2017-12-09jobs: master: fix post-build trigger of downstream jobsNeels Hofmeyr1-53/+14
Firstly, we don't have the downstream-ext plugin installed on our jenkins. We want to use the 'trigger' publisher instead. Secondly, since the jobs created here are called master-*, we also want to trigger master-*. master-libosmocore also triggers SIMtrace and xgoldmon, which aren't covered by this jobs config, hence they don't get a master- prefix. Change-Id: If9e8c4b02fce34fddceb4f07bf024210600f6270
2017-12-09jobs: gerrit, master, update-osmo-ci: fix build-discarder sectionNeels Hofmeyr1-5/+6
The build-discarder section was silently not working. It needs to be nested below a 'properties' node. Also the names need to be dashed and not camelCased. Change-Id: I9503200a8873e616f9195d4bb1d6163c464b305e
2017-12-02jobs: master-builds: libosmo-sigtran should trigger bsc and iuhNeels Hofmeyr1-0/+2
osmo-iuh in turn triggers osmo-msc and osmo-sgsn, no explicit triggers needed here. Change-Id: Ifd950660cdc3417e82b0a8f4ce2b1efde880cb7a
2017-12-02jobs: master-branches: trigger sgsn from iuhNeels Hofmeyr1-0/+1
osmo-sgsn uses libosmo-ranap and hence should be triggered from osmo-iuh. This naturally "includes" a trigger for libosmo-sigtran. Change-Id: Ia356dc2a8d5120f9d6262bf8eb25c32fe71e76c9
2017-12-02jobs: master-builds: osmo-bsc is now also a downstream of osmo-mgwNeels Hofmeyr1-0/+1
Change-Id: I03c63108bd845ee723d565c3dddd4e930bb68bef
2017-12-02jobs: master-builds: apply various initial fixesNeels Hofmeyr1-14/+11
libosmo-sccp, osmo-ggsn: The osmo-gsm-tester builds are downstream builds, yes, but we configured that with the osmo-gsm-tester builds: instead of telling libosmo-sccp to build osmo-gsm-tester_build-osmo-stp when done, we configure the osmo-gsm-tester_osmo-stp to build after libosmo-sccp. So that the master branch builds don't need to have any knowledge of osmo-gsm-tester. osmo-msc build triggers should rather be post-build triggers of osmo-iuh and osmo-mgw, like the others. Then we can also drop the pollscm here, and use the pollscm that is common to all other builds. Call these jobs 'master-*'. It more accurately says what they build, and also we can install the jobs from this file next to the current, old ones, without overwriting them and thus we'll have an easy rollback path. The new ones can co-exist with the old ones until the new ones are verified to work, at which point we can drop the old ones. Line 313: IIUC the safest git branch is 'refs/remotes/origin/master'. This is still untested! Change-Id: If2ad9c90a0986d1304cd53383d3df5b375f23ac8
2017-12-02jobs: rename normal-builds.yml to master-builds.ymlNeels Hofmeyr1-0/+333
Also apply the rename in the job names Change-Id: If623e573e49d4f1a409139c112afbc34e4cc450e
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 01:09:45 +0000