Home Home > Tag > OBS
Sign up | Login

Posts Tagged ‘OBS’

SUSE Studio online + Open Build Service = SUSE Studio Express

October 4th, 2017 by

Merging SUSE Studio and Open Build Service

Written by Andreas Jaeger

SUSE Studio was launched in 2009 to make building images really easy. Nowadays, images are used everywhere – for public cloud you need images; container images are used to have small and movable workloads, and data center operators use golden images to start their workloads.

As you may be aware, we have an Open Build Service (OBS) tool that helps you to build packages to deliver complete distributions. In the last few years, we have been updating this tool and it now can handle any kind of image.

Additionally, the default engine for building images at SUSE is kiwi and is used in both SUSE Studio and OBS.

Reviewing these offerings and the way the image build situation has evolved, we have decided to merge the two online services, OBS and SUSE Studio, into a common solution.

Looking at the feature requests for SUSE Studio on image building and looking at our technologies, we decided to use OBS as the base for our image building service. Since OBS already builds images for various environments, we will first add a new image building GUI to OBS. This combined solution will now be delivered as “SUSE Studio Express”.

(more…)

OBS got the power!

February 25th, 2017 by

Old build workers, rack mounted

One year after introducing a new kind of Open Build Service worker machines, the “lambkins”, the openSUSE Build Service got a big hardware refresh. The new machines, sponsored by SUSE, are equipped with:

– 2,8GHz AMD Opteron Processors (6348)

– 256 GB RAM

– one 120 GB SSD

Four of them are located in a chassis with a height of 2 units and run 12-16 workers on them (virtual machines, that are building packages).

That new build power allowed us to remove some of old machines from the pool. The unified hardware makes the management of the machines a lot easier now, even if there are still the most powerful old machines left.

For those who like some more pictures, feel free to check the rest of the entry… (more…)

Tumbleweed gets three snapshots, Leap deadline approaches

August 10th, 2016 by

Tumbleweed-black-greenSince the release of Linux Kernel 4.7 in the 20160730 snapshot, which brought lengthy email discussions about out-of-tree and third-party drivers on the Factory mailing list, openSUSE Tumbleweed produced three snapshots.

Snapshot 20160803 made a small update to the repositories for Mozilla Thunderbird and k3b. The snapshot updated libzypp to version 16.2.1, gnome-online-accounts to 3.20.3 and obs-service-source_validator. In 20160803, virt-viewer had the most changes.

Snapshot 20160805 brought more package changes and one major uninstall. LXDM was dropped from openSUSE Tumbleweed and uninstalled in this snapshot. LightDM is being used in the environment instead and is auto-installed with a change configuration for those who are using LXDM. This snapshot provided several repository updates, and NetworkManager-gnome, Libreoffice 5.2.0.4 and WireShark 2.0.5 were a few of the many changes found is 20160805.

The most recent snapshot, 20160806, updated Inkscape, which provides more extensions. Wayland-protocols updated to a new upstream release of 1.5 and btrfsprogs has new options to run in the background with version 4.7.

Tumbleweed users will likely get Plasma 5.72 in the next snapshot, which should be released soon.

openSUSE Leap

In two weeks is the submission deadline to get packages in the next version of openSUSE Leap 42.2. The Beta 1 is scheduled for release at the end of this month, according to the roadmap.

The current development version, Alpha 3, needs more people to test the version and file bugs. Download Alpha 3 and test it out at software.opensuse.org.

OBS welcomes new lambkins

January 27th, 2016 by

The openSUSE build service becomes more and more a victim of his success: building constantly more than 300,000 packages for more than 43,000 developers needs really a lot of build power! And build power means not only CPU! It includes everything that you can expect from an IT infrastructure:

Old hard-drives from OBS-workers

Old hard-drives from OBS-workers

  • CPU power
  • RAM (the more, the better)
  • Storage (temporary local, on the clients and also to store and distribute the results)
  • Network
  • electic power (and cooling, and maintenance, and manpower to maintain the hardware, …)

Thankfully our main sponsor SUSE allowed us now to buy some new hardware to replace some of the old machines that build software packages for over ten different distributions all day long.

(more…)

openSUSE Build Service 1.0 Released

July 9th, 2008 by

The openSUSE Project is proud to announce the 1.0 release of the openSUSE Build Service. The 1.0 release provides all the features necessary to support building openSUSE in the public build systems and allowing direct contributions to openSUSE from all contributors. Developers can now submit contributions to openSUSE directly at build.opensuse.org.

The openSUSE Build Service allows developers to create and maintain packages for openSUSE and many other Linux distributions, including CentOS, Debian, Fedora, Mandriva, Red Hat, and Ubuntu. With the 1.0 release, the openSUSE Build Service expands its scope to building the entire openSUSE release, and provides everyone with the same access and transparent interface to work on the openSUSE distribution.

The openSUSE Build Service has offered a simple collaboration system since its inception for groups to work closely together on packages or solutions stacks. The 1.0 release improves on existing functionality to allow the Build Service to scale to larger projects like openSUSE’s Factory distribution, and to allow building openSUSE’s stable releases in the open.

What the changes mean for contributors:

  • Anyone can find a package’s working copy as maintained by the official packager or packaging team. Contributors can submit changes against the working copy.
  • The submission handling and notification system has been put in place, allowing any contributor to request a merge of their changes to a project.
  • Quality assurance happens before contributions are merged. Test builds of a suggested change are accessible to anyone.
  • Improved branch handling. It is easy to set up a branch of a package. The branch will build in the same way as the original package, but can be modified.
  • Source handling is improved in 1.0. It’s now possible to easily maintain a branch, and modifications are stored without creating a full copy. This makes it easier to maintain features based on the latest copy of package. The Build Service builds the latest packages, including modifications, automatically.

The majority of this functionality is implemented on the server side. The rest can be implemented by the various Build Service clients, so that contributors can take advantage of the new features.

The Build Service team has also introduced a number of smaller improvements and bugfixes to make the system more scalable and usable.

The openSUSE Build Service is now considered “feature complete” for collaboration. The Build Service team is looking for additional feedback on improving the openSUSE Build Service as it will now be the standard tool for working on the distribution.

openSUSE Build Service 1.0 RC 1 released

June 11th, 2008 by

The openSUSE Project has released the first release candidate of the openSUSE Build Service 1.0. With the release candidate, all the features are now in place to support external collaboration with the community to build openSUSE in the open. Developers can now submit contributions to openSUSE directly at build.opensuse.org.

The openSUSE Build Service has offered a simple collaboration system since its inception for groups to work closely together on packages or solutions stacks. The 1.0 RC 1 release improves on existing functionality to allow the Build Service to scale to larger projects like openSUSE’s Factory distribution.

What the changes mean for contributors:

  • Anyone can find a package’s working copy as maintained by the official packager or packaging team. Contributors can submit changes against the working copy.
  • The submission handling and notification system has been put in place, allowing any contributor to request a merge of their changes to a project.
  • Quality assurance happens before contributions are merged. Test builds of a suggested change are accessible to anyone.
  • Improved branch handling. It is easy to set up a branch of a package. The branch will build in the same way as the original package, but can be modified.
  • Source handling is improved in 1.0. It’s now possible to easily maintain a branch, and modifications are stored without creating a full copy. This makes it easier to maintain features based on the latest copy of package. The Build Service builds the latest packages, including modifications, automatically.

The majority of this functionality is implemented on the server side. The rest can be implemented by the various Build Service clients, so that contributors can take advantage of the new features.

The Build Service team has also introduced a number of smaller improvements and bugfixes to make the system more scalable and usable.

The openSUSE Build Service is now considered “feature complete” for collaboration, but the team is expecting a lot of user feedback since this now is our standard tool for working on the distribution. We will be releasing frequent updates to improve the Build Service based on this feedback. Contributors can discuss the build service on the mailing list and on Freenode in the #opensuse-buildservice channel.

KDevelop and the openSUSE Build Service

June 4th, 2008 by

Building packages for multiple distros can be a major pain — which is why we provide the openSUSE Build Service. One of the Build Service’s many features is the ability to create packages for many distros — including openSUSE, SUSE Linux Enterprise, Debian, Fedora, CentOS, and Ubuntu. One of the projects making the most of the Build Service is KDevelop. We talked with KDevelop developer Amilcar do Carmo Lucas about how the KDevelop project is using the build service.

(more…)

openSUSE Project Releases Major Update to openSUSE Build Service

April 16th, 2008 by

The openSUSE team is proud to announce another major release of the openSUSE Build Service (OBS). This release brings a new level to OBS scalability by adding the ability for OBS instances to interact.

The 0.9 release will help grow a world-wide network of build service instances. OBS instances can automatically interact with each other and reuse projects residing on other OBS instances. New installations of OBS are automatically configured to work with the main openSUSE Build Service, which makes it easy to set up new instances and minimize network traffic while keeping data in sync automatically.

(more…)

Another Step in Connecting the Worlds of Users And Developers

December 18th, 2007 by

As you know for sure ;), the openSUSE Build Service (OBS) shall connect the complete different worlds of End-Users and developers/packager. This does of course already worked to that degree that everybody can download software, which got packaged in the OBS. Also the packager do already got feedback via download numbers, tags or rating within the packager web interface.

Andreas Bauer added lately the next functionality in this context. All search results in the End User interface do offer now a link to the packager web interface from now on. Every user, with a standard openSUSE account can now do the ratings and taging there directly. This will help the to improve the search results for other users later on.

Also new is the bugreport link, this means end users can create bugreports for projects or packages hosted in OBS. Such a bugreport will get assigned to the person, who is defined as bugowner. Atm only a few projects have this defined, so this is a call to all project or package owners to add yourself. This can be done easily in the web gui, simply add yourself again to the project, but switch to the “bugowner” role.

(more…)