Project

General

Profile

Latest Builds » History » Version 7

daniel, 03/13/2018 03:56 PM
update shasum of release.key

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