OpenSuse Build Service

(How do we move to an OBS)
(Basics)
Line 22: Line 22:
Some tasks needed to get the OBS running:
Some tasks needed to get the OBS running:
-
* [[/Installation|OBS Installation]]
+
* [[/Installation|OBS Installation]] - a detailed guide on how the system was setup.
-
* [[/Application QA Process|Application QA Process on the OBS]]
+
* [[/Application QA Process|Application QA Process on the OBS]] - a proposal
-
* [[/Fremantle_Setup|Setting up Fremantle]]
+
* [[/Fremantle_Setup|Setting up Fremantle]] - WIP.
-
* [[/Cross_Setup|Setting up cross-building]]
+
* [[/Cross_Setup|Setting up cross-building]] - started, not imported yet
-
* [[/Autobuild|An OBS Autobuilder queue]]
+
* [[/Autobuild|An OBS Autobuilder queue]] - not started
-
* [[/Reporting|Reporting]]
+
* [[/Reporting|Reporting]] - not started

Revision as of 11:56, 8 May 2010

OBS Intro

Our Goals

We want:

  • to allow freedom for developers to develop;
  • to provide a build service and SDK
  • to work with the core distro as much as possible
  • to provide excellent quality assured applications for our "app store";
  • to extend the core distro with a community supported Surrounds area for libraries and packages that are depended upon by more than one application.

Basics

Lets set out some basics about the OBS.

  1. It's a build system. You put source on it and say "use this repository" and it builds a minimal SDK-like chroot using the deb/rpms it finds in that repository
  2. It has packages - a package corresponds to a tarball and a spec/dsc
  3. It has projects - a project is like a directory with packages
  4. When a package is built it is 'published' from the project where it was uploaded into a corresponding repository (which can be used to build other projects)
  5. The repositories can also be used by devices to download binary packages.

The 'trick' then, is to set up a structure of projects that we can use to support the publishing and sharing activities that we need.

Some tasks needed to get the OBS running: