openSUSE:Build Service private instance
Use Cases
This HowTo addresses people who need to deliver software which is based on a rpm packet architecture and cannot be maintained on a public Open OBS. The reasons for doing this can vary but the main use cases are :
- running your test in your private environment before going public
- creating distributions with mixed proprietary and Open Source code
- creating specialised Embedded Linux distributions
- long term (several years) commitment to software maintenance
- creating highly customised distributions to meet individual customer needs
- enabling a code sharing model with partner / customer
- any case where you are not comfortable in using a public OBS
Alternatives
If you only want to build your packages against the repo created by an OBS instance (public or private) you might be willing to have a look at a tool based on a subset of OBS (in fact the build sub system). You will find a description [| here]
In order to smooth the issue of starting a project mixing private and open source code we have also created the project OBS Light that might fit your need. http://wiki.meego.com/OBS_Light
Architecture
more on Architecture and Requirements
Installation
more on Installation
OBS Boot strapping
more on Boot strapping
Software delivery
more on Software delivery
Life Cycle model
more on Software life cycle model with OBS
Enabling external partners
more on enabling external partners
See also
Official OBS documentation
https://openbuildservice.org/help/manuals/obs-admin-guide/
OBS Light
- http://en.opensuse.org/openSUSE:OBS_Light
- http://susegallery.com/a/e0uuBG/meego-obs
- http://www.dailymotion.com/playlist/x1t5ll_dominigarfoll_obs-light-training
Related articles
- http://doc.opensuse.org/products/draft/OBS/obs-best-practices_draft/index.html
- Portal:Build Service
- openSUSE:Specfile guidelines
- openSUSE:Build Service Deployment
- openSUSE:Build Service Appliance