OBS » History » Version 1
laforge, 08/10/2022 06:38 AM
1 | 1 | laforge | h1. Osmocom OBS |
---|---|---|---|
2 | |||
3 | {{>toc}} |
||
4 | |||
5 | The Osmocom [[binary packages]] are built with OBS (Open Build Service) hosted on "obs.osmocom.org":https://obs.osmocom.org. In order to do that, the jenkins jobs "Osmocom_OBS_latest":https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_latest_obs.osmocom.org/ / "_nightly":https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_nightly_obs.osmocom.org/ ("config":https://gitea.osmocom.org/osmocom/osmo-ci/src/branch/master/jobs/osmocom-obs.yml) checkout the source repositories and build debian *source* packages, then upload these to OBS. |
||
6 | |||
7 | OBS has a hierarchical namespace of _projects_, of which we currently use |
||
8 | * @osmocom:*@ for official package repositories of osmocom, like the @osmocom:latest@ and @osmocom:nightly@ |
||
9 | * @home:*@ as a personal playground / staging area for developers |
||
10 | |||
11 | h2. OBS access |
||
12 | |||
13 | Osmocom developers can register user accounts on OBS (sadly separate and not via redmine openID provider). This gives access to creating personal _OBS projects_, i.e. additional package feeds for development and testing |
||
14 | |||
15 | h3. The @osc@ command-line client |
||
16 | |||
17 | Many operations are easier when performed via the @osc@ command-line client rather than the web UI of OBS. |
||
18 | |||
19 | In order to make osc access @obs.osmocom.org@ instead of the default @build.opensuse.org@, you can specify the @-A https://obs.osmocom.org@ command-line option. See the man pages for more details. |
||
20 | |||
21 | h2. The @osmocom:*@ projects |
||
22 | |||
23 | For more information on these builds, how they are created, see [[OBS_Maintenance]]. |
||
24 | |||
25 | All packages marked as _publish_ in their configuration are rsync'ed over to https://downloads.sysmocom.de/packages |
||
26 | |||
27 | Write access to the @osmocom:@ projects requires respective group membership, please contact @laforge in case you need it. |
||
28 | |||
29 | |||
30 | h2. The @home:*@ projects |
||
31 | |||
32 | Every OBS user automatically gets their own @home:@ project, for example if your user name was foo, your home project would be @home:foo@ |
||
33 | |||
34 | You can build packages either directly in that home project, or you can create any number of sub-projects below, like @home:foo:bar@. |
||
35 | |||
36 | All packages marked as _publish_ in their configuration are rsync'ed over to https://people.osmocom.org/packages/ |