Project

General

Profile

Nightly Builds » History » Version 13

laforge, 09/06/2017 11:48 AM

1 8 laforge
{{>toc}}
2 8 laforge
3 1 laforge
h1. Nightly Builds
4 1 laforge
5 11 neels
sysmocom has setup nightly Debian source package builds for Osmocom GSM related software. Starting from March 18, 2016, there are daily builds for
6 1 laforge
7 11 neels
* Debian 8 (i586, amd64)
8 12 laforge
* Debian 9 (i586, amd64)
9 11 neels
* xUbuntu 16.04 (i586, amd64)
10 11 neels
* xUbuntu 16.10 (i586, amd64)
11 12 laforge
* xUbuntu 17.04 (i586, amd64)
12 11 neels
13 11 neels
The Osmocom jenkins will build source packages once a day and upload them to the Open(SUSE) Build Service (OBS). See https://jenkins.osmocom.org/jenkins/job/Osmocom_nightly_packages/ for corresponding build job.
14 11 neels
15 3 dexter
The nice people of SuSE have created the "network:osmocom" project for us and we have created the "network:osmocom:nightly" sub-project. The Jenkins will upload source packages for:
16 1 laforge
* libosmocore
17 1 laforge
* libosmo-abis
18 1 laforge
* libosmo-netif
19 1 laforge
* libosmo-sccp
20 1 laforge
* libsmpp34
21 1 laforge
* openbsc
22 1 laforge
* openggsn
23 13 laforge
* osmo-ggsn
24 1 laforge
* osmo-pcap
25 1 laforge
* osmo-stp (cellmgr-ng)
26 1 laforge
* osmo-bts
27 1 laforge
* osmo-trx
28 1 laforge
* osmo-pcu
29 1 laforge
* osmo-sip-connector
30 1 laforge
31 1 laforge
The OBS page is at https://build.opensuse.org/project/show/network:osmocom:nightly
32 1 laforge
33 10 msuraev
It's possible to reproduce the nightly builds locally using
34 10 msuraev
<pre>
35 10 msuraev
osc co
36 10 msuraev
osc build
37 10 msuraev
</pre>
38 10 msuraev
39 10 msuraev
To test local changes with nightly infrastructure one can create local packages the same way jenkins job above does:
40 1 laforge
<pre>
41 1 laforge
gbp buildpackage -S -uc -us --git-ignore-new --git-export-dir=/tmp
42 4 dexter
</pre>
43 1 laforge
and than repeat build steps outlined above for local build.
44 1 laforge
45 11 neels
The download repositories are at:
46 1 laforge
47 11 neels
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/
48 12 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_9.0/
49 11 neels
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_16.04/
50 11 neels
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_16.10/
51 12 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_17.04/
52 1 laforge
53 11 neels
Adding the repository to your Debian 8 system:
54 1 laforge
<pre>
55 1 laforge
sudo su
56 1 laforge
wget http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/Release.key 
57 1 laforge
sha256sum Release.key
58 1 laforge
=> 487d3c309facae16e83b3863bc042033fd02c41eb7183ced196d83225abb5729
59 1 laforge
apt-key add Release.key
60 2 wirelesss
echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list
61 1 laforge
apt-get update
62 4 dexter
exit
63 6 dexter
</pre>
64 1 laforge
65 8 laforge
h2. E-Mail Notifications of build failures
66 8 laforge
67 11 neels
Build failure notifications are sent to the high-noise OpenBSC gerrit-log Mailing List <gerrit-log@lists.osmocom.org>
68 11 neels
69 8 laforge
There seems to be no easy way in OBS to register an e-mail address (such as a mailing list) that gets notified in case of build errors.  What we ended up doing is to
70 11 neels
* register an OBS user account "openbsc-list" with e-mail address of the mailing list
71 8 laforge
* include that account with a 'reader' role in the OBS "openbsc:nightly" project
72 11 neels
* set the OBS user notification preferences of that "openbsc-list" user to include "Package has failed to build" for "reader" role.
Add picture from clipboard (Maximum size: 48.8 MB)