openSUSE:Build Service installations
Please add yourself here if you run a local version of the openSUSE Buildservice. Please also describe what you are you using it for.
Amino Communication Ltd
At Amino Communication  we are using an OBS appliance to build our version of MeeGo which is used in our Intel based Setop box. We use it to follow the upstream Linux kernel and multiple customer configuration in a semi automated way.
The openSUSE Buildservice gives us Linux specialists at B1 Systems the power to easily provide customized, well adapted packages to our customers and partners. Whether maintaining fixed package releases for longterm or testing bleeding edge OSS - OBS makes it possible. B1 Systems is one of the Support Partners recommended by SUSE. First Level and Second Level Support can be provided directly by the B1 Team.
Banco do Brasil
A local OBS has been implemented to simplify building our private packages, as well as maintaining customized internal installation media. By having this service we are able to easily package for multiple architectures and multiple SLE and openSUSE-based distributions.
Collabora has been using OBS for about 2 years as part of its core Build & Infrastructure (B&I) for internal and customer use.
The majority of Collabora's OBS workers are ARM systems due to our customers' demand. The instances by Collabora primarily produce .deb packages for both Debian and Ubuntu images.
Collabora creates complete bare-metal images from the packages produced by its OBS instance. Collabora has also helped several of its customers to roll out their own on-premise OBS instances.
cPanel uses Open Build Service for building the the Apache & PHP RPMs used inside of its EasyApache4 subsystem.
See this email
Datto is a cybersecurity and data backup company that offers Unified Continuity, Networking, and Business Management solutions.
Datto’s OBS instance is deployed using the official appliance installer provided on the website. Workers run in a VM without nested virtualization, so container build environments are used.
Datto builds nearly all software with RPM spec files using OBS’s spec builder engine and debbuild! Even though using spec files as the build mechanism, the packages are native, (mostly) Debian packages. Most of the packages are built using the same spec file for an RPM distribution (usually Fedora) and Ubuntu.
The Datto Linux Agent is a bit special. It has been built for over 25 Linux distribution targets across the Red Hat/Fedora, SUSE, and Debian/Ubuntu distribution families leveraging this strategy!
The packaging workflow is designed around Git repositories being the source of truth. Every commit gets built in Datto's CI infrastructure as a so-called “scratch build” where the outputs are thrown away after verifying that the build was successful, including on every proposed change via a pull request.
For more information on how Datto is using OBS, read the blog post or watch the video presentation on Flexible and Fast Software Delivery with OBS.
Dell OpenManage Server Administrator (OMSA) Michael Brown
As of OpenManage 6.2 released in Dec 2009, most of the OMSA software stack is built using OBS. We build native packages for each OS we support using a Dell-internal private OBS instance, and have completely rewritten our build system and packaging to be as close to Linux RPM Packaging guidelines and FHS as possible. While we still have a small handful of RPMs which are not built using OBS, we are making good progress on having a full stack built using OBS, likely to be released later this year.
Dell Community Repository http://linux.dell.com/repo/community Michael Brown
Dell hosts several open source projects for distribution to customers on a community-support-only basis. We struggled to build all of the software across all the OS distribution flavors using a homegrown build system. OBS saved the day in allowing not only easy access to build across our most popular repos, but also in allowing secure access to allow trusted third parties to add content to our repos.
DSA uses OBS for building cross-distribution packages (rhel/sles, x86_64) and kiwi images.
Elektrobit Automotive GmbH
Elektrobit uses the OBS to build and maintain SUSE based distributions.
The GENIVI Alliance uses OBS to create developer baseline images.
Barcelona based ItechGrup SL uses a local Open Build Service to build packages for Linkat GNU/Linux (openSUSE based distribution) and for some other open source projects.
IsarFlow Software Solutions GmbH
We are compiling rpms for SLES, RedHat and CentOs and create CDs.
Linaro uses OBS for building Debian, Ubuntu, Centos and Fedora packages for 96boards and reference platforms. The OBS service runs on Arm64 server and native workers are used for Arm64, Arm and X86_64 targets.
linux-administrator projects uses a local setup of Open Build Service to create packages / distributions for various projects like VHCS and stresslinux or other personally needed setups. The same instance is used to build packages needed in our datacenter environment at InterNetX GmbH.
The following distributions are included in our setup (i586/x86_64):
- (open)SuSE Linux 9.3 - 11.3 (+Updates)
- SuSE Linux Enterprise 9 - 11 (+Updates)
- Fedora 5 - 13 (+Extras)
- CentOS 4.x and 5.x (+EPEL)
- Redhat Enterprise Linux 5.x and 6.x
- Debian Etch/Lenny
- Ubuntu 6.06 - 10.04
Our repos are powered by mirrorbrain.
Maemo.org and MeeGo Community
The Maemo community needs to provide build services for the community to create packages for Fremantle and other releases of Maemo. The OBS service is package agnostic and can build our debian packages for both x86 and ARM architectures. Now that Maemo is becoming MeeGo we will also be supporting the MeeGo community and providing build services that will eventually allow developers to deploy to both x86 and arm architectures using both rpm and debian packaging.
The maemo instance is behind build.obs.maemo.org.
The meego instance is behind build.meego.com.
The Moblin project uses a local instance of the Open Build Service to build and manage the Moblin packages. After careful evaluation of the available solutions, Open Build Service appeared to be the best fit for Moblin's objectives.
open-slx gmbh Nuremberg (openSUSE box product)
open-slx has running an obs instance since 2/2010. This obs is used to build addons, that can not be checked in in build.opensuse.org. For example commercial software of 3rd party vendors. Also Balsam extensions are produced here. OBS is giving our developers a unified integration platform for openSUSE packages.
OBS Testing/Development, Embedded Systems, Imaging ( Jan-Simon Möller )
OBS is the Backend for the new version of the LiRE Platform. I'm also using OBS for Cross Development - see this post.
- Fedora 8 @ arm5el
- Debian Etch @ arm4l
- Maemo/Diablo @ arm6el
- openSUSE 10.3 @ i586/x86_64
- openSUSE 11.0 @ i586/x86_64
- openSUSE 11.1 @ i586/x86_64
- openSUSE Factory @ i586/x86_64
- Homebrew @ i586
- LiRE @ i586
Open-Xchange Server and App Suite packages for Linux ( Carsten Hoeger / Open-Xchange )
We use a local OBS to build our complete Open-Xchange server packages. We also integrated Jenkins with OBS in using customized ant tasks that use the OBS REST API
The openSUSE packages in the Packman repository are built using a local setup of the Open Build Service (currently using trunk) to provide many additional packages for openSUSE (games, multimedia, ...).
SailfishOS is an independent mobile OS. Sailfish OS has an OBS at https://build.sailfishos.org/ for building packages. It takes source code from git repositories to create standalone packages, allowing the building of packages on a variety of supported platforms for testing and release distribution. It performs:
Automated building of Sailfish OS packages when triggered by Webhooks from git repositories On-demand building of Sailfish OS packages, when manually triggered
Each package is added under a project. For example, there is a ofono package that is linked to the oFono code repository, and this package lives within the mer-core:devel project, which contains all of the mer-core packages that are built for a devel image. If a package cannot be built, the OBS web page for that package shows the build error details and the status of the package.
For more information about how SailfishOS uses the Open Build Service, visit https://sailfishos.org/wiki/Open_Build_Service.
Scorpio IT ( computersalat )
Ability to build packages the way we prefer or with newer version not available for used dist. Usage of Maintenance repos (Updates) like it is done on build.opensuse.org
SPIE SAG CeGIT
SPIE SAG CeGIT uses OBS for (cross) building packages (sles, x86_64 and Windows).
State Capital Munich
it@m from the state capital of munich use the OBS to build several packages for internal usage on SLES and RHEL.
Stylite GmbH uses a local Open Build Service to test-build packages for EGroupware and build our own EPL (EGroupware Premium Line) packages. Official EGroupware packages will then be build on https://build.opensuse.org and distributed from there.
sysmocom - systems for mobile communications GmbH
sysmocom uses a self-hosted Open Build Service to build binary packages of a number of open source packages (mostly from the Osmocom project) for its customers. Those typically contain customer-specific patches compared to the official Osmocom binary packages which are built on the public build.opensuse.org infrastructure network:osmocom:nightly and network:osmocom:latest
United States Postal Service
We've implemented a local OBS to simplify building our own private packages. By having this service we are able to package for x86_64 and s390x over multiple SLES distributions easily.
University of British Columbia Okanagan for Research and Distro Deployment ( Steve Cundy )
We have been using a local OBS primarily for building custom/open/commercial packages required for our standard SLED and SLES deployment as well as managing unique software requests from our researchers and faculty with incredible response times. The OBS has also proved to be a critical and invaluable tool in allowing us to quickly roll out new servers and desktops configured for use at UBCO. With extremely limited resources we can fully support a rapidly growing linux infrastructure and community on campus. The project has been so successful we are looking into providing a public server for faculty/students/grads develop on, expanding the choices of fully supported distros to choose from, and getting more involved in community project development (ie: AccessGrid).
University of Erlangen-Nuremberg (Computer Center)
The universities computer center (RRZE, Regionales Rechenzentrum Erlangen) has been running a local OBS instance since 2007. Its main purpose is to provide up-to-date or pre-configured packages for our Linux infrastructure (mainly SLES 9/10/11). The OBS enables us to support a large range of different releases and system architectures with little effort.
VideoLAN repositories for openSUSE Tumbleweed, Leap 15.1 and 15.2 SUSE Linux Enterprise 11, 12 and 15 ( Dimstar )
The VideoLAN repository is built on an own installation of OBS. Even signing is used in this instance. The OBS instance is running and building the repo found at http://download.videolan.org/SuSE/.
We are using a local OBS to build Debian packages for development of new products, maintenance of existing packages, and cross-platform integration.
At INRIA (Institut National de Recherche en Informatique et Automatique), we have started using OBS to port our packages from Mandriva in which XtreemOS was originally based to other rpm distributions, such as CentOS and all the SLE/openSUSE variants. XtreemOS is a set of grid/cloud middleware technologies which also include a distributed file system, as well as support for Virtual Organizations and shared computing resources across organizations.
At Jotron AS, we have started to use OBS to package our linux software. Our customers need control over system upgrades and track packages, so we have to package our applications to intergrate with their package manager. OBS makes this very easy! We are also currently using it to build custom appliance that will ship on embedded devices.