OBS » History » Revision 2
Revision 1 (laforge, 08/10/2022 06:38 AM) → Revision 2/4 (laforge, 08/10/2022 06:40 AM)
h1. Osmocom OBS
{{>toc}}
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.
OBS has a hierarchical namespace of _projects_, of which we currently use
* @osmocom:*@ for official package repositories of osmocom, like the @osmocom:latest@ and @osmocom:nightly@
* @home:*@ as a personal playground / staging area for developers
h2. OBS access
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
h3. The @osc@ command-line client
Many operations are easier when performed via the @osc@ command-line client rather than the web UI of OBS.
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.
h2. The @osmocom:*@ projects
For more information on these builds, how they are created, see [[OBS_Maintenance]].
All packages marked as _publish_ in their configuration are rsync'ed over to https://downloads.sysmocom.de/packages
Write access to the @osmocom:@ projects requires respective group membership, please contact @laforge in case you need it.
h2. The @home:*@ projects
Every OBS user automatically gets their own @home:@ project, for example if your user name was foo, your home project would be @home:foo@
You can build packages either directly in that home project, or you can create any number of sub-projects below, like @home:foo:bar@.
All packages marked as _publish_ in their configuration are rsync'ed over to https://people.osmocom.org/packages/home%3A/ https://people.osmocom.org/packages/
