Age | Commit message (Collapse) | Author | Files | Lines |
|
The job verifies the gerrit patchset.
Change-Id: If661675528059bc8a95d39a6489a5a9381f52677
|
|
Both jobs doing the actual test run on the prod or rnd tester.
Change-Id: Ic1c4babc547f48402b0bcfaf38e2734e87e565f0
|
|
osmo-gsm-tester_build-trigger-all triggers a new build of all
osmo-gsm-tester build jobs.
Change-Id: I8dcf2a6fa2991cb73b4807f8a10d251f3dca77dd
|
|
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
|
|
Change-Id: Ib103b3343d582f7a78f0c4cec00c94078a078584
|
|
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
|
|
Change-Id: I6f025c642d5ae57cdda9d7b34bbaeb82ca119354
|
|
The slaves to build on are determined by the slave_axis, the node parameter has
no useful effect.
Change-Id: I029de2a46f22a1b1dc977bce71137eb78b826157
|
|
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
|
|
Change-Id: I989075eb0cd930d42daa36d9d8501592141c0310
|
|
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
|
|
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
|
|
Change-Id: I6b703b9f27865b146f20bea953fe3d6500a88166
|
|
Change-Id: Ie3803a46ee192dc72823291004ee20f4bdbe0126
|
|
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
|
|
Change-Id: I852b42a698a4568b51e993bb5e86efeed6afdb32
|
|
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
|
|
Change-Id: Ie96288913aae2fe97fa11266ffa9ed098044ccfd
|
|
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
|
|
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
|
|
Change-Id: I2b208455b7bd008fb25322280894c100e51f2227
|
|
Change-Id: I808c46c2f4488fd577bb1c23cd13c5b73519265b
|
|
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
|
|
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
|
|
Similar to Idac6e53b1e0addbcb5b6c99b8051e1e0ad26bc5b fix the master
branch builds.
Change-Id: Icdd53a7cb037324a568e8eab529716e030e00583
|
|
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
|
|
Change-Id: I8bb6792ab061edd3d688e387fa69cd8637617dee
|
|
instruction sets enabled
Change-Id: I1d73165a397d98d8fb630f7adec45f00887c139a
|
|
sets enabled
Change-Id: I651e182dfd62ef4b88d013d8b5960ce7e3562ecf
|
|
Change-Id: I32938d4c1854ce65faa718eccaecb5e3143dbcd0
|
|
The [yes, no] tuple was automatically converted to [True, False] by the
jenkins-job-builder but the combination filter still used old literal
check. Fix this by using boolean from the very beginning.
Change-Id: Idac6e53b1e0addbcb5b6c99b8051e1e0ad26bc5b
|
|
Change-Id: I0a72d36d777ba582815b2cdef8130ee88c060b54
|
|
Notify intern@ if either update-osmo-ci or update-osmo-python jobs
failed. Those are essential for our CI and test infrastructure so we
should look into related failures right away.
Change-Id: I0d51e35424a26eab7d38152e13f3ac6fd3f3997c
Related: OS#2821
|
|
Change-Id: I9a122cee4fa98115140e4a34f623958697affed2
|
|
Change-Id: Idb4e93d88123f0a7e403af627345300dae86aca7
|
|
Change-Id: I252c103450ad0da59ab18c88d78f20c750b22c98
|
|
Change-Id: Icaa44207ebbdc03c3af1a32f7491d2b4c9fb982d
|
|
Change-Id: I24aadc2aeeeda762df61e7c56e4159a730010c97
|
|
Change-Id: Ida1301a3f83caff400e80c8b46504f98cb0894ab
|
|
Change-Id: I8b18a5bc54a879002b40b0fc51cd295e82beba4f
|
|
Change-Id: Ib59247978ed92b72949260a79628b28754a44484
|
|
Change-Id: Ib3982e1f18286cc45d5c7b849abfb91cad9e1b27
|
|
poll-scm was missing by accident
Change-Id: I027c5fa12c8be9434e3efec11976004c7924c472
|
|
Change-Id: I48246067f05227efc18b46cb1b29d1c50f4eab84
|
|
Change-Id: Ia5db32b8ffe62f9578a55c9049d0c13fc6da7e83
|
|
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
|
|
we simply call 'make compile' which will compile all of the projects
from TTCN-3 to C++
Change-Id: I2bb94c08259c130558f82bb4c084484be5b81c40
|
|
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
|
|
Change-Id: I219a988f94b465ac8bb77319735aedbe49707c16
|
|
Change-Id: I4b9db4077eacca649c679333e24b2eb7338a96e6
|