User Guide
- About this Guide
- I First Steps
- II Concepts
- III Setup
- IV Usage
- V Best Practices
- VI Reference
- 20 OBS Architecture
- 21 OBS Concepts
- 22 Build Process
- 23 Build Containers
- 24 Source Management
- 25 SCM Bridge [EXPERIMENTAL]
- 26 Supported Formats
- 27 Request And Review System
- 28 Image Templates
- 29 Multiple Build Description File Handling
- 30 Maintenance Support
- 31 Binary Package Tracking
- 32 Administration
- 33 Scheduling and Dispatching
- 34 Build Job Constraints
- 35 Building Preinstall Images
- 36 Authorization
- 37 Quality Assurance(QA) Hooks
- 38 openSUSE Factory
- Glossary
- A GNU Licenses
Part IV Usage #
- 5 Basic OBS Workflow
- 6 Local Building
Every build which happens on the server can also be executed locally in the same environment using the osc tool. All what you need is to checkout the source code and build the build recipe. The following explains it for RPM format, but it works for any. osc will download needed binaries and execute the local build.
- 7 Using Source Services
Source Services are tools to validate, generate or modify sources in a trustable way. They are designed as smallest possible tools and can be combined following the powerful idea of the classic UNIX design.
- 8 SCM/CI Workflow Integration
With this integration, you can take advantage of source code management (SCM) systems like GitHub, GitLab or Gitea to manage your packages sources. Then, you can integrate those sources with OBS to run different workflows, for instance, to build a package and report back the result to the SCM.
- 9 Staging Workflow
This API provides an easy way to get information about a single or all staging projects like state, requests and checks. Note: To use this API, you first need to setup a staging workflow for a project.
- 10 Notifications
That means this feature is only available through our Unstable project which we deploy on public OBS instance, but is still not part of an OBS release.