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
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
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
osmo-sgsn uses libosmo-ranap and hence should be triggered from osmo-iuh. This
naturally "includes" a trigger for libosmo-sigtran.
Change-Id: Ia356dc2a8d5120f9d6262bf8eb25c32fe71e76c9
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
after the recent successful conversion from manual job definitions
to jenkins-job-buildre of the gerrit jobs, this is an attempt to convert
also the non-gerrit jobs for the common osmocom projects.
WARNING: this file has not been tested yet, it's a WIP.
Change-Id: Ib04707393264a845876659d7bee0cdc9f8b897b6
Download (ADD) the latest patch from git.osmocom.org so that the image gets
rebuilt when new changes were merged to master.
Change-Id: I215f5f6504018d589fa44776a332757a7b870d53
To reduce docker image rebuild time, move the Smalltalk related commands to a
separate file, which is currently not built by rebuild_osmocom_jenkins_image.sh
since there are no jenkins builds using that yet.
Change-Id: I1142f068100ef07ce7f177adaa8a0fe2fedb1b7b
The jenkins invocation of the docker image commonly includes the osmo-ci
scripts via binding ~/bin to an up-to-date checkout. We don't need another
version of osmo-deps.sh in /usr/local/bin.
Change-Id: I5ce9ab992afa3c5a7a0bb13b55cae016bc8e805f
The node is offline and has been for a long time. The last osmo-ci-on-slaves
job ran for a week waiting for it to come back online.
Change-Id: I5a315d1ce3d7d5763ba07bf29f9cdd5d6f7c6491
We're not calling this script on the update-osmo-ci-on-slaves job yet. To move
over to calling this script, apply some edits we made on the jenkins UI in the
meantime.
Change-Id: I54d3f56a89934c1c7b0e445b5c447c91bf94d579
Using a $TOP variable makes directory paths more clear
to understandable. Path now expressed starting from the TOP dir
instead of using ../../../foo
Change-Id: I7a87532a3232fbcfb5f676588991dbc59a34f739
Instead of modifying the job on Jenkins, let's do it like in our
other projects. Create the diretcory if it doesn't exist and use
git pull origin for the Debian9 system.
Change-Id: I0ecdc02e3271fe09980f370167277370c599fcfa
It was recently spotted, in a osmo-msc jenkins build, that an updated
dependency (new commits to be fetched) contained a new tag which was
not fetched with the commit. It resulted in the Makefile generating an
old .version file, which ended up generating a library version in the
.pc which later in the build make the configure script fail while
checking at the dependencies.
As far as I could understand after reading several discussion threads,
it seems git fetch doesn't necessarily fetch and store locally all new
tags found in the remote, and we need to explicitly add the --tags
parameter to be sure all of them are downloaded.
This patch adds a new fetch line instead of patching the one already
present because it seems in old versions of git the --tags parameter had
a different behaviour, in which only tags and not branches are fetched.
This way is ensured that we get both correct regardless of git version.
Change-Id: I4bfe4846959c70e435d6792a755a6f2a6f0a932c
This trigger is responsible for triggering another build
once the first build is complete and sets a +V
Change-Id: I235e0211a01da0eb74d8e6a9581aa34b59073ca0
If I have a git clone that once did 'checkout [-f] branch', and if then
origin/branch gets updates, doing another 'checkout -f branch' only goes back
to the local tracking-branch of origin/branch. We never pull in changes from
origin/branch anymore as soon as a local branch exists. Always prepend
'origin/', so that 'checkout -f' goes into detached-HEAD state onto the newest
fetched revision.
Change-Id: Ia715a100b5beaf7e612c2c64cdad8819aa00c8bd
In early September we asked on the public mailing list if there are
any users of the FreeBSD builds, and there was no response at all.
Let's disable the build testing on FreeBSD. This will significantly
speed up our build testing, as well as pave the way for a more
comprehensive docker/containerization of build testing.
We're still extremely happy to merge any patches for support of
FreeBSD or other operating systems. But the core Osmocom developers
will not perform related testing / porting.
Change-Id: I2c6d2a17c3cf9d8c78c3675995493e30cbc6be0d
The point of using docker is to allow concurrent builds, hence set 'concurrent:
true' for all jobs using docker.
Change-Id: I6333ee2856cbeb0cc3eb14c381ac8faf838c5f97
fixed in osmo-bsc, osmo-mgw, osmo-sgsn, cellmgr-ng:
Spanning a single shell command across several lines with backslashes in the
end breaks when the newlines are not preserved: the backslashes escape a
following space, which is joined to the following cmdline arg.
Add the leading less-indented comments that curiously lead to preserving the
newline characters in the cmd sections.
Change-Id: Icfd6cfb7ca4172795620e1d7ee60610db4f7226b
libgtpnl is the userspace library for using kenrel GTP-U support,
which is used by openggsn (and will be used by osmo-ggsn).
Change-Id: Iad600a36cb658bbd874b4587ec514f49703d6a45
Having tabs in the yml files cause parse errors. For vim convenience, add
comments that instruct vim to expand the tabs to spaces.
Change-Id: I5f0598a31e30d1a9440c40935644bb782f645664
Interestingly enough, only a line that has more indenting than the first line
also receives an actual newline in the resulting jenkins Execute Shell section.
Hence insert '# keep first line with less indent' comments.
Change-Id: I13bcb41fa0e59b60a201c2b769bad42067e34ab8
After the "manual" cleanup from I2409b2928b4d7ebbd6c005097d4ad7337307dd93 has
been applied in numerous jenkins.sh scripts of the various osmocom projects,
drop the git plugin cleanup step.
Rationale:
- The git plugin cleanup apparently does not check against non-writable files,
like leftovers from a failed 'make distcheck'. If any are left behind, the
build fails even before the build steps start.
- The git cleanup would wipe out all git clones, which we're trying to re-use
across rebuilds now.
The osmo-clean-workspace.sh takes care of this, so don't use the jenkins
plugin.
Change-Id: I8a43b851cef2ad7e8582f1e9bbe3547e3b77fc1a
Pau Espin
Neels Hofmeyr
Harald Welte