Project

General

Profile

Nightly Builds » History » Version 15

laforge, 10/26/2017 07:19 PM
update package list, remove nitb-split

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