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