12 Build Job Constraints

The hostlabel is any string which can be assigned to build hosts when starting the bs_worker process. It can be used to run on specific hosts, which may be used for running benchmarks in a reproducible way. This constraint can also be defined as a negative definition using the exclude=true attribute. However, the hostlabel is always specific to one OBS instance. You should avoid it as much as possible, since building with this constraint in another instance is usually not possible. Use any of the other constraints if possible.

Example for _constraints file:

<constraints exclude="false">
  <hostlabel>benchmark_runner</hostlabel>
</constraints>

Example for project configuration:

Constraint: hostlabel benchmark_runner

Defines the sandbox which is used for the build job. Sandboxes are chroot, Xen or KVM environments. There is also the virtual secure sandbox, which allows building on Xen or KVM. This constraints may also be defined as a negative definition via the exclude=true attribute.

Example for _constraints file:

<constraints exclude="true">
  <sandbox>secure</sandbox>
</constraints>

Example for project configuration:

Constraint: sandbox secure

The Linux kernel specific part.

<constraints>
  <linux><version>
    <min>3.0</min>
    <max>4.0</max>
  </version></linux>
</constraints>

Constraint: linux:version:min 3.0
Constraint: linux:version:max 4.0

<constraints>
  <linux>
    <flavor>default</flavor>
  </linux>
</constraints>

Constraint: linux:flavor default

To require hardware or build instance features.

<constraints>
  <hardware><cpu>
    <flag>mmx</flag>
    <flag>sse2</flag>
  </cpu></hardware>
</constraints>

Constraint: hardware:cpu:flag mmx
Constraint: hardware:cpu:flag sse2

<constraints>
  <hardware>
    <processors>4</processors>
  </hardware>
</constraints>

Constraint: hardware:processors 4

<constraints>
  <hardware>
    <disk>
      <size unit="G">4</size>
    </disk>
  </hardware>
</constraints>

Constraint: hardware:disk:size unit="G" 4

<constraints>
  <hardware>
    <memory>
      <size unit="M">1400</size>
    </memory>
  </hardware>
</constraints>

Constraint: hardware:memory:size unit="M" 1400

<constraints>
  <hardware>
    <physicalmemory>
      <size unit="M">1400</size>
    </physicalmemory>
  </hardware>
</constraints>

Constraint: hardware:physicalmemory:size unit="M" 1400

The constraint handling depends on what is met by the restrictions. The handling starts when there is no worker to fulfill the constraints.

waiting for 4 compliant workers (4 down)

package build was not possible:

no compliant workers (constraints mismatch hint: hardware:processors sandbox)

Please adapt your constraints.

You can check the constraints of a project / package with the osc tool. You have to be in an osc working directory.

osc checkconstraints [OPTS] REPOSITORY ARCH CONSTRAINTSFILE

Either you give a repository and an arch or osc will check the constraints for all repository / arch pairs for the package. A few examples:

# osc checkconstraints
Repository                Arch                      Worker
----------                ----                      ------
openSUSE_Leap_42.2        x86_64                    1
openSUSE_Leap_42.1        x86_64                    1

If no file is given it takes the local _constraints file. If this file does not exist or the --ignore-file switch is set only the project constraints are used.

# osc checkconstraints openSUSE_Leap_42.1 x86_64
Worker
------
x86_64:worker:1
x86_64:worker:2

If a repository and an arch is given a list of compliant workers is returned.

Another command to verify a worker and display the worker information is osc workerinfo.

<worker hostarch="x86_64" registerserver="http://localhost:5252" workerid="worker:1">
  <hostlabel>MY_WORKER_LABEL_1</hostlabel>
  <sandbox>chroot</sandbox>
  <linux>
    <version>4.1.34-33</version>
    <flavor>default</flavor>
  </linux>
  <hardware>
    <cpu>
      <flag>fpu</flag>
      <flag>vme</flag>
      <flag>de</flag>
    </cpu>
    <processors>2</processors>
    <jobs>1</jobs>
  </hardware>
</worker>

It returns the information of the desired worker.