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