Project

General

Profile

Nightly Builds » History » Version 24

osmith, 12/10/2018 02:58 PM

1 8 laforge
{{>toc}}
2 8 laforge
3 16 laforge
h1. _Nightly_ Builds
4 1 laforge
5 17 laforge
sysmocom has setup nightly Debian/Ubuntu source package builds for the current master version of the Osmocom GSM related software. 
6 17 laforge
7 17 laforge
*NOTE: USE NIGHTLY BUILDS ONLY FOR DEVELOPMENT/TESTING*.  The [[Latest_Builds]] are a more stable alternative.
8 17 laforge
9 17 laforge
Starting from March 18, 2016, there are daily builds for
10 1 laforge
11 11 neels
* Debian 8 (i586, amd64)
12 18 laforge
* Debian 9 (i586, amd64, armv7l, aarch64)
13 11 neels
* xUbuntu 16.04 (i586, amd64)
14 22 lynxis
* xUbuntu 17.10 (i586, amd64)
15 22 lynxis
* xUbuntu 18.04 (i586, amd64)
16 1 laforge
17 16 laforge
The Osmocom jenkins will build source packages once a day and upload them to the Open(SUSE) Build Service (OBS). 
18 14 neels
19 1 laforge
The OBS page is at https://build.opensuse.org/project/show/network:osmocom:nightly
20 1 laforge
21 16 laforge
A nice status overview on the builds is available at https://build.opensuse.org/project/monitor/network:osmocom:nightly
22 1 laforge
23 16 laforge
h2. How to use the _osmocom:nightly_ builds
24 1 laforge
25 1 laforge
The download repositories are at:
26 1 laforge
27 1 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/
28 1 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_9.0/
29 1 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_16.04/
30 16 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_17.10/
31 21 laforge
* http://download.opensuse.org/repositories/network:/osmocom:/nightly/xUbuntu_18.04/
32 1 laforge
33 1 laforge
Adding the repository to your Debian 8 system:
34 1 laforge
<pre>
35 10 msuraev
sudo su
36 23 osmith
wget https://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/Release.key 
37 10 msuraev
sha256sum Release.key
38 19 daniel
=> cbb03d32d144d45ba654ff9ed16361218d224a1bdffbdf2832c48e796b955aa8
39 10 msuraev
apt-key add Release.key
40 20 pespin
rm Release.key
41 1 laforge
echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list
42 11 neels
apt-get update
43 1 laforge
exit
44 11 neels
</pre>
45 12 laforge
46 16 laforge
h2. How are those builds created?
47 11 neels
48 16 laforge
See https://jenkins.osmocom.org/jenkins/job/Osmocom_nightly_packages/ for corresponding build job.
49 1 laforge
50 16 laforge
The script at http://git.osmocom.org/osmo-ci/tree/scripts/osmocom-nightly-packages.sh is used to
51 16 laforge
* obtain a current clone of the respective git repository
52 16 laforge
* check out the current master in that repository
53 16 laforge
* build debian source packages
54 24 osmith
* upload them to the OBS *network:osmocom:nightly* sub-project.
55 16 laforge
56 16 laforge
It's possible to reproduce the nightly builds locally using
57 16 laforge
<pre>
58 16 laforge
osc co
59 16 laforge
osc build
60 16 laforge
</pre>
61 16 laforge
62 16 laforge
To test local changes with one can create local packages the same way jenkins job above does:
63 16 laforge
<pre>
64 16 laforge
gbp buildpackage -S -uc -us --git-ignore-new --git-export-dir=/tmp
65 16 laforge
</pre>
66 16 laforge
and than repeat build steps outlined above for local build.
67 16 laforge
68 16 laforge
h2. E-Mail Notifications of build failures
69 16 laforge
70 16 laforge
Build failure notifications are sent to the "gerrit-log mailing list":https://lists.osmocom.org/mailman/listinfo/gerrit-log
Add picture from clipboard (Maximum size: 48.8 MB)