Project

General

Profile

Nightly Builds » History » Version 14

neels, 09/14/2017 12:07 AM

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