Project

General

Profile

Nightly Builds » History » Version 10

msuraev, 01/26/2017 03:49 PM

1 8 laforge
{{>toc}}
2 8 laforge
3 1 laforge
h1. Nightly Builds
4 1 laforge
5 9 msuraev
sysmocom has setup nightly Debian source package builds for Osmocom GSM related software. Starting from March 18, 2016, there are daily builds for Debian7.0 (i586, amd64) and Debian8.0 (amd64). 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.
6 1 laforge
7 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:
8 1 laforge
* libosmocore
9 1 laforge
* libosmo-abis
10 1 laforge
* libosmo-netif
11 1 laforge
* libosmo-sccp
12 1 laforge
* libsmpp34
13 1 laforge
* openbsc
14 1 laforge
* openggsn
15 1 laforge
* osmo-pcap
16 1 laforge
* osmo-stp (cellmgr-ng)
17 1 laforge
* osmo-bts
18 1 laforge
* osmo-trx
19 1 laforge
* osmo-pcu
20 1 laforge
* osmo-sip-connector
21 1 laforge
22 1 laforge
The OBS page is at https://build.opensuse.org/project/show/network:osmocom:nightly
23 1 laforge
24 10 msuraev
It's possible to reproduce the nightly builds locally using
25 10 msuraev
<pre>
26 10 msuraev
osc co
27 10 msuraev
osc build
28 10 msuraev
</pre>
29 1 laforge
30 10 msuraev
To test local changes with nightly infrastructure one can create local packages the same way jenkins job above does:
31 10 msuraev
<pre>
32 10 msuraev
gbp buildpackage -S -uc -us --git-ignore-new --git-export-dir=/tmp
33 10 msuraev
</pre>
34 10 msuraev
and than repeat build steps outlined above for local build.
35 1 laforge
36 1 laforge
The Debian 7.0 repository is at http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_7.0
37 1 laforge
38 1 laforge
The Debian 8.0 repository is at http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/
39 1 laforge
40 1 laforge
41 1 laforge
Adding the repository to your system Debian 7.0
42 1 laforge
<pre>
43 5 dexter
sudo su
44 1 laforge
wget http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_7.0/Release.key 
45 1 laforge
sha256sum Release.key
46 1 laforge
=> 487d3c309facae16e83b3863bc042033fd02c41eb7183ced196d83225abb5729
47 2 wirelesss
apt-key add Release.key
48 1 laforge
echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_7.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list 
49 4 dexter
apt-get update
50 6 dexter
exit
51 1 laforge
</pre>
52 1 laforge
53 1 laforge
Adding the repository to your system Debian 8.0
54 1 laforge
<pre>
55 5 dexter
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 2 wirelesss
apt-key add Release.key
60 1 laforge
echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list
61 4 dexter
apt-get update
62 6 dexter
exit
63 1 laforge
</pre>
64 8 laforge
65 8 laforge
h2. E-Mail Notifications of build failures
66 8 laforge
67 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
68 8 laforge
* register an OBS user account "openbsc-list" with e-mail address of the openbsc mailing list
69 8 laforge
* include that account with a 'reader' role in the OBS "openbsc:nightly" project
70 8 laforge
* 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)