Remove the container, as the job has been rewritten to not require its
own docker container anymore, see the osmo-ci patch.
Depends: osmo-ci I9f8b671b9780da500637a64fc4dbc72b450f9d11
Change-Id: Ic35a28a386170b85d32aab8f2bd33e48e6d45392
Add a parameter that can be used to reproduce the failure locally with
the last list from jenkins, without having SSH set up to download the
list of existing tarballs.
Change-Id: I9af310c24aa65c21cc4bd365d3df7804cba02df7
Probably copy pasted from another script, doesn't make much sense here
since only the release tarballs are built. Nothing gets compiled here,
the variable was not used.
Change-Id: Ie74ee6976759f9634503b21e964e93efcc925679
Run configure with the --with-mstrx argument, so LIBTRXCON_DIR is not
pointing at an empty directory.
Fix for:
make[2]: Entering directory '/build/_temp/repos/osmo-trx/osmocom-bb'
make[2]: *** No rule to make target 'distdir'. Stop.
Change-Id: I2f067409f98119d4e35cf86cc2c816fc3c19e3f5
Run all commands inside the docker containers as a user with the same
UID as on the host system, not as root. This is a good idea in general
and also fixes permission problems when jenkins tries to wipe the
workspace.
Related: OS#5793
Change-Id: I0d949e5ab4b1a709d18a316def0a98c3b244457e
Don't fail if no tarball was generated and therefore the
_release_tarballs directory does not exist.
Related: OS#5793
Change-Id: Ib7c551e5376776eb267140bc4b897d5bb1634cbc
Previously this job relied on always running on the same jenkins node,
and having the previously built release tarballs in a workspace
directory that does not get removed. It would only skip building a
release tarball if the file already exists locally.
As part of OS#5793 this job needs to be moved away from that jenkins
node. When trying to run the job on a different node, it will build all
release tarballs again which takes unnecessarsily long and actually
fails on libosmocore-0.9.4 due to a missing python2.
This probably happens because the job was refactored at some point and I
didn't realize that the python2 dep is now missing as the previous
tarballs existed.
In general it doesn't make much sense to build previous release tarballs
again and to always keep the legacy environments around for that. Change
the code to check if a tarball exists on the server, and skip building
the tarball in that case.
Related: OS#5793
Related: https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/Osmocom-release-tarballs/1281/console
Change-Id: I4b8c149c9cdbe7c613eea5d9be15794de5e5ddce
Prepare to use ssh inside the docker container to check if tarballs
already exist, see the next patch.
Remove the '' around UserKnownHostsFile as using SSH_COMMAND in the next
patch without rsync fails otherwise with:
command-line: line 0: Bad configuration option: 'userknownhostsfile
Change-Id: I6dfe5d587d05063c6cf2c9ec683e7b7e499b79c1
Adjust the Makefile as well after the docker container has been migrated
to debian 11 in Ib6039724a7200abce5252f95407047296b72cd51.
Change-Id: Ibebca7be7daccd17bbf1b382108d87eb5a93ecf1
Add a jenkins.sh that does the same as the previous lengthy shell
command in the jenkins-job-builder file, and add
osmocom-release-tarballs.sh. This makes it easier to test the
script, and only patching one repository is needed from now on when
changing to a newer debian version.
Depends: osmo-ci I15f6c08b807f1462f91e95b624cdc1aad0592dd6
Change-Id: I4cf66097f508c029f688ec8af1cab2238d42f84f
Let it use debian bullseye and rename the directory once, so we don't
need to rename it in the future when switching the debian version
again.
The reason I'm doing this now is that building with debian 9 failed
due to obs.osmocom.org related changes. It would be trivial to fix that,
but I decided to rather upgrade to the latest debian version.
Change-Id: Ib6039724a7200abce5252f95407047296b72cd51
Oliver Smith