aboutsummaryrefslogtreecommitdiffstats
path: root/scripts
AgeCommit message (Collapse)AuthorFilesLines
2022-08-17obs: add explicit --git-branch argNeels Hofmeyr4-13/+19
Change-Id: I612c18e533542f442e0571927fee8b8be9fb8c2b
2022-08-16obs: add libosmo-pfcp, osmo-upfNeels Hofmeyr1-0/+2
Change-Id: I7192f4c9e77035cebb147b8186296bcd741d419b
2022-08-13update git URLs (git -> https; gitea/gerrit)Harald Welte5-7/+7
Unencrypted git:// protocol offers no integrity or authentication, making it subject to tampering. Use https:// instead. https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git https://blog.readthedocs.com/github-git-protocol-deprecation/ Change-Id: Ia44e4127ff87a3d4d747225d3258188a0a891f1b
2022-08-10{jobs,coverity}: add a new project - libosmo-gprsVadim Yanitskiy1-0/+1
Change-Id: I83e86084e9f7a7431bf5a70c372da1f9ccd28436
2022-08-10OSMO_RELEASE_REPOS: add missing libosmo-pfcp and osmo-upfVadim Yanitskiy1-0/+2
Change-Id: Ib7431281ff78686087d23bb6d600e6c68faef6e5
2022-08-04obs: add osmo-bsc-nat, osmo-fl2kOliver Smith1-0/+3
Looks like I copied the list of packages from the old latest script, so these two that were only in nightly are missing. Once added, they will be built for nightly again and not for latest as there's no tag matching the patterin in the git repositories. Change-Id: I4b96f15e95c70f1dca12a292964e6f12b04e4a04
2022-08-03obs: fix_source_format: ignore missing \nOliver Smith1-5/+4
Apparently a \n at the end of debian/source/format is not required, so don't fix it if it is missing. This avoids printing this confusing line: osmo-trx: fixing debian/source/format (3.0 (native) => 3.0 (native)) Change-Id: I7f9bb22a389a2109109f7fecd3b7ae0413fe6f5b
2022-08-01scripts/obs: rewrite pushing source pkgs to OBSOliver Smith19-1007/+1322
Harald requested that the OBS scripts should not stop if building one specific source package fails, instead it should keep going and report at the end a non-success exit code. Given that the shell script code has historically grown and became hard to maintain, I decided to rewrite the scripts for implementing this feature. This rewrite solves additional problems: * No full checkout of an OBS project like network:osmocom:latest anymore, with lots of packages that won't get updated (e.g. the uhd package has a uhd-images_3.14.1.1.tar.xz file that is 108 MB). With the old code, developers had to wait minutes during the checkout before the script reaches code that is currently being developed. Now only single packages get checked out right before they get updated. * No need to clone git repositories over and over. With the new code, git repos only get cloned if needed (for latest it is not needed if the remote git tag is the same as the version in OBS). During development, the cloned git repositories are cached. * Output from commands like "git tag -l" is not written to the log unless they failed. This makes the log more readable, which is especially important when a package fails to build, we keep going and need to spot the build error in the middle of the log later on. * No more duplicated code for nightly and latest scripts that worked similar but had slight differences. Also the list of packages is not duplicated for nightly and latest anymore; nightly uses all packages and latest uses packages that have at least one git tag. * Building source packages is decoupled from uploading them. A separate script build_srcpkg.py can be used to just build the deb + rpm spec source packages, without interacting with the OBS server. * The scripts can optionally run in docker with a command-line switch, and this is used by jenkins. This way we don't need to install more dependencies on the host such as rebar3 which is now needed for erlang/osmo_dia2gsup. * Add erlang/osmo_dia2gsup and run its generate_build_dep.sh (SYS#6006) I have done the new implementation in python to make use of argparse and to be able to use try/except and print a trace when building one package fails. Example output: * https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_nightly_obs.osmocom.org/48/console * https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_latest_obs.osmocom.org/46/console Change-Id: I45a555d05a9da808c0fe0145aae665f583cb80d9
2022-07-18scripts: osmo_obs_add_rpm_spec: fix tar patternOliver Smith1-1/+1
Fix the pattern that gets the source tarball with ls in order to update the "Source:" line in the spec file. The previous assumption was that it would always match: ls -1 "${name}_"*".tar."* But this isn't the case anymore since a spec file was added to libosmo-dsp where the package name ($name) is libosmo-dsp, but the tarball doesn't have the minus character: libosmodsp_0.4.0.1.d7d9.202207150002.tar.xz Therefore just change the pattern to: ls -1 *_*.tar.* We can do this because there is always only one tarball in the directory and we wouldn't use ".tar." in a package name. Fixes: OS#5619 Change-Id: Ic704f480102ab6f90f3936a3be30e3020402e750
2022-07-15scripts/osmocom-packages-docker: pass OBS_SERVEROliver Smith1-0/+1
Make the variable available, as it's needed by the scripts that osmocom-packages-docker.sh calls since Ib271e16e93ebc58ed1ecb0ea881e1f1370e40928. Change-Id: I8e53523b9b1ceafa45fe7b3dca2731d4e1c74959
2022-07-12docker-rebuild: add debian-bullseye-jenkinsOliver Smith1-1/+2
Related: OS#6041 Depends: docker-playground I849568826b1993fd9fb652779e631188af4a319e Change-Id: I22f95de0bd131f0f0cfd5e2a24e17bed22e5d248
2022-07-12docker-rebuild: build erlang img on x86_64 onlyOliver Smith1-8/+1
Build debian-bullseye-erlang on x86_64 nodes only, as the image doesn't get used on nodes with other arches. The image is only used by gerrit-verifications jobs for osmo_dia2gsum and osmo_gsup, which are restriected to run on these nodes: https://jenkins.osmocom.org/jenkins/label/osmocom-gerrit-debian9/ Remove the check and comments for not building for debian 10 x32, as that node has been replaced with a debian 11 one. Related: OS#5453 Change-Id: I5636dfc9e06a44b096f9dc55528d677ea2dfc352
2022-07-08scripts/repo-install-test: add debian 11, drop 9Oliver Smith4-34/+89
Change-Id: I3e154def9051076bd8091b3f027ee76bbb94cb18
2022-07-08scripts/OBS latest: fix checkout with dir in pathOliver Smith1-2/+3
osmo-python-tests was added to latest just like it was in nightly, by adding the following two lines to build_osmocom(): checkout python/osmo-python-tests ... build osmo-python-tests But the build fails, because the "checkout" function clones into a "python/osmo-python-tests" directory in latest, and not into a "osmo-python-tests" directory like in nightly. Make it behave the same by adjusting the "checkout" function in nightly. (This code has historically grown and should be refactored imho, but let's fix this bug first.) Fix for: ====> Building osmo-python-tests + cd /home/osmocom-build/jenkins/workspace/Osmocom_OBS_latest_obs.osmocom.org/osmo-python-tests ./scripts/osmocom-latest-packages.sh: 99: cd: can't cd to .../osmo-python-tests Change-Id: I97074ee953cadac476fe2e4b686689c26bac1ea1
2022-07-07scripts/osmocom-latest-packages.sh: build osmo-python-testsOliver Smith1-0/+1
Build the source package too, don't just checkout the sources. Related: OS#5604 Change-Id: I5b7c6b6849edbca44f45041a6e506f10933b5d43
2022-07-06ci-docker-rebuild: drop debian-stretch-jenkinsOliver Smith1-1/+0
Related: OS#5601 Change-Id: I572ff9624fba25d7d96af79d1229b614be1c11ba
2022-07-06scripts/osmocom-latest-packages: add osmo-python-testsOliver Smith1-0/+1
Add it in the same place as in osmocom-nightly-packages.sh. Closes: OS#5604 Change-Id: I187c73f8dff6800abaaeb6126ace13142a8ae20d
2022-07-01jobs/osmocom-release-tarballs: move to dpOliver Smith1-286/+0
Move the long shell command into a jenkins.sh in docker-playground, and move the osmocom-release-tarballs.sh script there as well. 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: docker-playground I4cf66097f508c029f688ec8af1cab2238d42f84f Change-Id: I15f6c08b807f1462f91e95b624cdc1aad0592dd6
2022-06-29osmo-ci-docker-rebuild: don't always build osmo-gsm-testerOliver Smith1-1/+1
Currently there is only one jenkins node labeled as osmo-gsm-tester-build. Build the osmo-gsm-tester container only there, not on all x86_64 nodes. The /var/tmp/osmo-gsm-tester/state directory is set up by ansible/roles/gsm-tester/tasks/main.yml. Related: https://jenkins.osmocom.org/jenkins/label/osmo-gsm-tester-build/ Change-Id: I9191d6d54d516ce75f3f576f34463dcaad22c85a
2022-06-27jobs/osmocom-obs: run against obs.osmocom.org tooOliver Smith1-0/+10
Split the OBS related jenkins jobs into two, one that uploads to the new obs.osmocom.org and one that uploads to build.opensuse.org. Set an alias for "osc" that sets the right server, and set the expand_aliases shopt so the bash scripts that source common-obs.sh will not ignore the alias. Related: OS#5557 Change-Id: Ib271e16e93ebc58ed1ecb0ea881e1f1370e40928
2022-06-21jobs, scripts: add 2022q2Oliver Smith2-0/+2
Related: SYS#6007 Change-Id: I59198f38ba817f56f6b24eae163297393587ec0b
2022-06-10repo-install-test: get OBS pub key from proper URLOliver Smith1-3/+2
The public OBS key expired on 2022-05-22 and was replaced with a key that was only shortly valid until 2022-06-08. Shortly after it was replaced with a key that is valid longer, until 2024-08-02. On 2022-06-09, one of the osmocom-repo-install tests started failing. For some reason, the key in the latest/Debian_10 directory was not updated to the latest one: https://download.opensuse.org/repositories/network:/osmocom:/latest/Debian_10/Release.key Since the key is the same for all of network:osmocom, adjust the function to download it from a place that the OBS web UI links to when attempting to download the public GPG key. I guess the latest/Debian_10/Release.key will get updated once making a new release and updating the packages in the repository. But sinc there's a lot of other tasks to do, just use this practical solution for now. Change-Id: Idd0fb6e07cba959a36269244b0c7b5c62aaffeee
2022-04-13OBS, ttcn3-testsuites: add 2022q1Oliver Smith2-0/+2
Related: SYS#5887 Change-Id: Idadb541b49e57b4403a6a6e4c966bcba9c6651db
2022-03-29OBS nightly-packages.sh: add osmo-bsc-natOliver Smith1-0/+2
Related: SYS#5560 Change-Id: I47cd67d5dcf3eb49b486e99840449e1c6a41b4ab
2022-02-21scripts/osmo-ci-docker-rebuild: x86: skip deb11Oliver Smith1-2/+13
Don't attempt to build debian-bullseye (11) in docker on debian 10 x86, as it results in: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed. This is a temporary measure until we've upgraded the only jenkins node that runs debian 10 on x86, gtp0-deb10build32. Related: OS#5453 Change-Id: Iba7679c027ca89a29393c220d01b195cfce4fec3
2022-02-18allow to terminate value_string[] with '{0}'Neels Hofmeyr1-1/+1
For a long time I was using '{}' to indicate a nulled out struct. But apparently '{0}' is the favored way to write that. Let's allow using this notation to terminate a value_string[]. Change-Id: Id2f5ba897ec83f34f8d3c4425353c0baf309bb6d
2022-02-15Use docker image debian-bullseye-erlang instead of debian-buster-erlangPau Espin Pedrol1-1/+1
Let's use newer debian to avoid problems with older erlang. Furthermore, the new image builds rebar3 to avoid issues with unmatching erlang versions. Change-Id: I7b1956c515daccf6ab1ff87031c6fec649cadb4b
2022-02-11scripts/docker-cleanup.sh: conditional img cleanOliver Smith1-4/+8
Only run the simple image clean code if docuum is not running. It works well enough in most cases, but has the drawbacks that it never deletes "latest" images or images not matching "^osmocom-build", and may delete images that are still being used (OS#5447). With the other tool, all images are considered for removal, and the ones that have not been used the longest time are removed first. Related: OS#5477, OS#5066, SYS#5827 Change-Id: I1cef0833c096de0fa5acf77156bb5dd362e2ef9c
2022-02-11scripts/docker-cleanup.sh: use "docker system prune"Oliver Smith1-1/+2
Do not only clean up dangling images, but also containers, volumes and networks. Related: SYS#5827 Change-Id: If441b251de50063f0229d36fb1bc260a4cb1dd87
2022-02-11scripts/docker-cleanup.sh: delete containers tooOliver Smith1-0/+6
Related: SYS#5827 Change-Id: I73b2f13875286c1aaa5424809edab2202f41768b
2022-02-11scripts/docker-cleanup.sh: use set -xOliver Smith1-1/+1
Change-Id: Iba170128e55a9778467c3d3bcf33a91321a8c29f
2022-02-11scripts/osmocom-packages-docker: docker run --rmOliver Smith1-0/+1
Change-Id: I357ae8071d27088a2c0a74f962ac1589bff43a70
2022-01-05Add new repo osmo-hnbgw (latest) to build jobs and scriptsPau Espin Pedrol2-3/+3
Change-Id: I634ebbfa7f471342ffcf253fdb8a316f5e71089f
2022-01-05Add new repo osmo-hnbgw (nightly) to build jobs and scriptsPau Espin Pedrol3-0/+5
Change-Id: I2fdbd651e4b50191e1a67e183590de99d6366ca5
2021-12-23OBS, ttcn3-testsuites: add 2021q4Oliver Smith2-0/+2
Related: SYS#5726 Change-Id: I4913218b192cf0cb1fb74b239ced9a0501c2eb48
2021-12-21repo-install-test: Validate osmo-hnodeb --versionPau Espin Pedrol1-0/+1
Change-Id: I87c9c375fa810223daadd5768d6a54e9935c34eb
2021-12-14osmocom-release-tarballs: fix missing st2 cloneOliver Smith1-0/+2
Clone simtrace2.git before trying to create the tarball with git. Fix for: simtrace2 simtrace2-0.1.tar.bz2 (creating) + cd /osmo-ci/_temp/repos/simtrace2 /osmo-ci/scripts/osmocom-release-tarballs.sh: 195: cd: can't cd to /osmo-ci/_temp/repos/simtrace2 Related: OS#5347 Fixes: 0221a0 ("OSMO_RELEASE_REPOS: add simtrace2, osmo-remsim") Change-Id: I0a845549ba1fe9f0d9ab55a5c5c7bf5b8f57caae
2021-12-13OSMO_RELEASE_REPOS: add simtrace2, osmo-remsimOliver Smith2-8/+74
Adjust to simtrace2's directory structure, which does not have a configure.ac in the main directory like all other repositories. The main directory has a regular Makefile without autotools, only the host dir has a configure.ac file (and only in newer versions). Deal with this by creating two tarballs, one with "git archive" for the whole directory, and one for the host dir only with the usual "autoreconf -fi; ./configure; make dist-bzip2". The latter one has the files created by autoreconf ("configure" script and others). simtrace2 ├── simtrace2-0.1.tar.bz2 ├── simtrace2-0.2.tar.bz2 ├── simtrace2-0.3.tar.bz2 ├── simtrace2-0.4.tar.bz2 ├── simtrace2-0.5.1.tar.bz2 ├── simtrace2-0.5.tar.bz2 ├── simtrace2-0.6.1.tar.bz2 ├── simtrace2-0.6.tar.bz2 ├── simtrace2-0.7.0.tar.bz2 ├── simtrace2-0.7.1.tar.bz2 ├── simtrace2-0.8.0.tar.bz2 ├── simtrace2-0.8.1.tar.bz2 ├── simtrace2-host-0.6.1.tar.bz2 ├── simtrace2-host-0.6.tar.bz2 ├── simtrace2-host-0.7.0.tar.bz2 ├── simtrace2-host-0.7.1.tar.bz2 ├── simtrace2-host-0.8.0.tar.bz2 └── simtrace2-host-0.8.1.tar.bz2 Closes: OS#5347 Change-Id: Ib52a23a2a7d6ea64bfa539b1d026f035fdb3af57
2021-12-13OSMO_RELEASE_REPOS: sync with Nov 2021 releasesOliver Smith2-1/+12
Depends: docker-playground I19b6b0363aeeb89ab6aac2b125359589e6b9b5a7 Related: OS#5347 Related: https://osmocom.org/news/152 Change-Id: Ib2022ca670b322d81ff83bbca3bb262f8d7287a6
2021-12-13OSMO_RELEASE_REPOS: sortOliver Smith1-1/+2
Make it easier to figure out which projects are missing. Related: OS#5347 Change-Id: I3660032d020154b7a175483691842b576552ffd1
2021-11-17OBS: latest: enable osmo-hnodebOliver Smith1-0/+2
Enable osmo-hnodeb for latest, now that we have a tagged version. Change-Id: I3037a43280dbb56ecaf4f2e067f0a1533d19d10a
2021-10-30scripts: add a script for checking presence of <endian.h>Vadim Yanitskiy1-0/+23
Change-Id: I6a1e7fc2e96f42fc596f47b4d7f1ac6c61d834b6
2021-10-26OBS: nightly: fix missing checkout osmo-hnodebOliver Smith1-0/+1
Fixes: 2ab3f7 ("Build and test osmo-hnodeb nightly packages") Related: https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_nightly/1044 Change-Id: I327adaa8f60c1f90aa150e9d4fba5a10f271c96b
2021-10-25Build and test osmo-hnodeb nightly packagesPau Espin Pedrol3-0/+3
Change-Id: I53c2b357b0669f5101ceec7896c4ba30e69605c2
2021-09-16build-old-tags: mark osmo-msc 1.7.0 as known errorOliver Smith1-0/+1
Old osmo-msc releases failed to build because logging output of libosmo-mgcp-client has changed. I'm backporting the fix as 1.7.1 and 1.6.4. The script builds the last 3 releases (1.6.4, 1.7.0, 1.7.1), so mark 1.7.0 as known error. Related: osmo-msc Id197e4ab9ba12e284299ef520edee9c362513bf1 Change-Id: I86f8252d450165f4be3d7c97fa70235638f7dd96
2021-09-01OBS: remove {osmo-gsm-manuals,osmo-trx}-debian8Oliver Smith2-6/+0
Drop these workarounds, as we are not building binary packages for debian 8 anymore. Related: OS#5223 Change-Id: Ibe7ba124557969df62798ba49c4489e9606c2341
2021-08-09repo-install-test: osmo-pcap-server: !latestOliver Smith1-2/+2
Disable osmo-pcap-server for latest again, as the port is still conflicting there with osmo-bts. Fixes: 7ca9c4 ("repo-install-test: clear SERVICES_NIGHTLY list") Related: OS#5203 Change-Id: I711e0e13c3e3af30407b85fd10aca9446f2b94ba
2021-08-05repo-install-test: clear SERVICES_NIGHTLY listOliver Smith1-10/+6
All services that start up in nightly should also start in the latest release now, as new versions have been released of related programs. Change-Id: Idc94270978ec5ca67d6f7e20e009f905e972f984
2021-06-16osmo-ci-docker-rebuild: don't build ogt for armOliver Smith1-1/+5
Don't attempt to build the osmo-gsm-tester docker container on arm. It's currently causing the update-osmo-ci-on-slaves job to fail on rpi4-raspbian10build-ansible-*. Related: https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=rpi4-raspbian10build-ansible-1/876/console Change-Id: Ic30de69d318927d5c142f8212eefa3a53037ef25
2021-05-19OBS: use nightly script to build 2021q1 feedOliver Smith3-5/+14
Use the nightly script instead of latest, so all packages get upgraded when upgrading osmocom-2021q1. Related: SYS#5370 Change-Id: If8de585652997aae1edb586c948c181f564f6994
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 13:54:06 +0000