Travis provides nice integration with GitHub, it can automatically run tests for every commit or every pull request.

It is already used in e.g. registration module, see the build result.

Unfortunately the current support is quite limited, the problem is that Yast packages are not available at Travis builders. The workaround is to mock used Yast calls (that leads to overmocking) and reimplementing some Yast core functions. Another solution is to test only the functionality which does not rely on Yast much, but that means the code coverage will be rather small...

Provide Yast packages for Ubuntu

Travis allows to install additional packages (see the doc), but the builders are running Ubuntu and we do not have Yast packages for Ubuntu...

The solution is to repackage Yast packages to deb packages for Ubuntu in YaSTadd-emojiTravis OBS project.


  1. We do not need to package all Yast modules, just the base packages like yast2-core, yast2, yast2-ruby-bindings and the dependent packages, the leaf packages do not need to packaged.

  2. It's really about repackaging, the Yast packages will very likely not work in Ubuntu out of box (because of different config files, package names, file locations, services, different system defaults, different package management...). But that should not matter as the system access will be stubbed/mocked in the tests anyway, for running tests the real functionality is not needed, we just need that the files can compiled and loaded.

Current Status

I have already started the project at the CSM department workshop last month. What has been done:

  1. YaSTadd-emojiTravis OBS project set up

  2. Some modules already have .travis.yml file added and Travis builds are enabled in Travis branch

  3. There is the overview of already converted modules is available

The Goal

  1. Enable Travis builds for all currently maintained Yast packages (in Git master branch)
  2. As a side effect we could attract some Debian/Ubuntu developers to help us with the Yast port and this could help us to broaden the community around Yast.

The Future

  1. The support could be enhanced to other Git branches, for example SLE12-GA branch could be used for testing SLE12 maintenace updates.
  2. The tests run at Travis can be enhanced to report test code coverage using coveralls



Looking for mad skills in:

packaging travis obs yast

This project is part of:

Hack Week 11


  • about 5 years ago: mvidner liked Travis CI support for Yast
  • about 5 years ago: lslezak added keyword "yast" to Travis CI support for Yast
  • about 5 years ago: lslezak added keyword "obs" to Travis CI support for Yast
  • about 5 years ago: lslezak added keyword "travis" to Travis CI support for Yast
  • about 5 years ago: lslezak added keyword "packaging" to Travis CI support for Yast
  • Show History


    • lslezak
      about 5 years ago by lslezak | Reply

      The Result

      I have managed to enable Travis support to all Yast modules, which I consider a big success!

      See the details in this document.

      This should improve testing automation for all Yast modules and we should be more confident when doing changes in Yast as basically every commit to Git master will be automatically tested.

    Similar Projects

    Package Robot OS (ROS) in OBS by a_faerber

    A number of vendors are adopting [ROS](http://w...

    Finish packaging Angr in OBS by a_faerber

    Following a FOSDEM presentation on [Angr](http:...

    MicroOS Desktop by RBrownSUSE

    [Video Recording of openSUSE Conference sessio...

    Distribution source code repository/browser by mkoutny

    Motivation: You know a particular function ...

    obsci - a CI for open build service packages by tbechtold

    Currently it's pretty difficult to create tests...

    Ant Ivy OBS resolver by cbosdonnat

    SUSE Manager uses an ivy repository on the R&D ...

    Migrate more OBS service scripts to pure systemd by enavarro_suse

    Following the work started in the last hackweek...