Project

General

Profile

Nightly Builds » History » Version 11

neels, 04/20/2017 10:04 PM

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 11 neels
* xUbuntu 16.04 (i586, amd64)
9 11 neels
* xUbuntu 16.10 (i586, amd64)
10 11 neels
11 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.
12 11 neels
13 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:
14 1 laforge
* libosmocore
15 1 laforge
* libosmo-abis
16 1 laforge
* libosmo-netif
17 1 laforge
* libosmo-sccp
18 1 laforge
* libsmpp34
19 1 laforge
* openbsc
20 1 laforge
* openggsn
21 1 laforge
* osmo-pcap
22 1 laforge
* osmo-stp (cellmgr-ng)
23 1 laforge
* osmo-bts
24 1 laforge
* osmo-trx
25 1 laforge
* osmo-pcu
26 1 laforge
* osmo-sip-connector
27 1 laforge
28 1 laforge
The OBS page is at https://build.opensuse.org/project/show/network:osmocom:nightly
29 1 laforge
30 10 msuraev
It's possible to reproduce the nightly builds locally using
31 10 msuraev
<pre>
32 10 msuraev
osc co
33 10 msuraev
osc build
34 10 msuraev
</pre>
35 10 msuraev
36 10 msuraev
To test local changes with nightly infrastructure one can create local packages the same way jenkins job above does:
37 1 laforge
<pre>
38 1 laforge
gbp buildpackage -S -uc -us --git-ignore-new --git-export-dir=/tmp
39 4 dexter
</pre>
40 1 laforge
and than repeat build steps outlined above for local build.
41 1 laforge
42 11 neels
The download repositories are at:
43 1 laforge
44 11 neels
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/
45 11 neels
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_16.04/
46 11 neels
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_16.10/
47 1 laforge
48 11 neels
Adding the repository to your Debian 8 system:
49 1 laforge
<pre>
50 1 laforge
sudo su
51 1 laforge
wget http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/Release.key 
52 1 laforge
sha256sum Release.key
53 1 laforge
=> 487d3c309facae16e83b3863bc042033fd02c41eb7183ced196d83225abb5729
54 1 laforge
apt-key add Release.key
55 2 wirelesss
echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list
56 1 laforge
apt-get update
57 4 dexter
exit
58 6 dexter
</pre>
59 1 laforge
60 8 laforge
h2. E-Mail Notifications of build failures
61 8 laforge
62 11 neels
Build failure notifications are sent to the high-noise OpenBSC gerrit-log Mailing List <gerrit-log@lists.osmocom.org>
63 11 neels
64 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
65 11 neels
* register an OBS user account "openbsc-list" with e-mail address of the mailing list
66 8 laforge
* include that account with a 'reader' role in the OBS "openbsc:nightly" project
67 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)