Nightly Builds » History » Version 23
osmith, 12/10/2018 02:56 PM
let's download release keys over https
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 | 11 | neels | * xUbuntu 16.04 (i586, amd64) |
14 | 22 | lynxis | * xUbuntu 17.10 (i586, amd64) |
15 | * 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 | |||
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 | The download repositories are at: |
||
26 | |||
27 | * http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ |
||
28 | * http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_9.0/ |
||
29 | * 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 | Adding the repository to your Debian 8 system: |
||
34 | <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 | * obtain a current clone of the respective git repository |
||
52 | * check out the current master in that repository |
||
53 | * build debian source packages |
||
54 | * upload them to the OBS *network:osmocom:nightlyt* sub-project. |
||
55 | |||
56 | It's possible to reproduce the nightly builds locally using |
||
57 | <pre> |
||
58 | osc co |
||
59 | osc build |
||
60 | </pre> |
||
61 | |||
62 | To test local changes with one can create local packages the same way jenkins job above does: |
||
63 | <pre> |
||
64 | gbp buildpackage -S -uc -us --git-ignore-new --git-export-dir=/tmp |
||
65 | </pre> |
||
66 | and than repeat build steps outlined above for local build. |
||
67 | |||
68 | h2. E-Mail Notifications of build failures |
||
69 | |||
70 | Build failure notifications are sent to the "gerrit-log mailing list":https://lists.osmocom.org/mailman/listinfo/gerrit-log |