The Libyui Testing Image

This repository builds a Docker image which is used for running the CI tests at Travis. The built image is available at the libyui/devel Docker repository.

Docker Tags

This repository builds several versions of the image which are published by the Docker Hub with a different tag.

The images are defined in the Dockerfile.<tag> files and published as libyui/devel:<tag> at the Docker Hub. See the complete list of tags at the Docker Hub.

Automatic Rebuilds

• The image is rebuilt whenever a commit it pushed to the master branch. This is implemented via GitHub webhooks.

• Additionally the image is periodically rebuilt to ensure the latest YaST packages from the devel:libraries:libyui OBS project are used even when the image configuration has not been changed. The build is triggered by the docker-trigger-libyui-devel Jenkins job.

• The upstream dependency to the opensuse project is defined so whenever the base openSUSE system is updated the image should be automatically rebuilt as well.

Triggering a Rebuild Manually

If for some reason the automatic rebuilds do not work or you need to fix a broken build you can trigger rebuild manually.

• Go to the Build Settings tab and press the Trigger button for the required Docker image.

• If you need to trigger the build from a script check the Build Triggers section at the bottom, press the Show examples link to display the curl commands. (The commands contain a secret access token, keep it in a safe place, do not put it in a publicly visible place.)

The Image Content

The images contain all development packages needed for building the libyui packages.

Using the image

The images contain an libyui-travis script which runs all the checks and tests.

The workflow is:

• Copy the sources into the /usr/src/app directory.
• Run the libyui-travis script.