Meta Configuration of home:pawil:incus:lts-6.0:staging

<project name="home:pawil:incus:lts-6.0:staging">
  <title>Incus lts-6.0 - staging, tested before release</title>
  <description>Staging area for home:pawil:incus:lts-6.0. Not intended for installation.

Builds the same package as the production project, but nothing here reaches
anyone on its own. Each build is installed on clean openSUSE images - Leap 16.0
and Tumbleweed, x86_64 and aarch64 - and then exercised: incusd is started and a
real container is launched. Only if all of that passes is a release to the
production project triggered.

Publishing is enabled deliberately, because the tests need somewhere to install
from. Nothing directs users here. Install from the production project instead:

zypper addrepo https://download.opensuse.org/repositories/home:pawil:incus:lts-6.0/openSUSE_Leap_16.0/home:pawil:incus:lts-6.0.repo
  zypper refresh
  zypper install incus incus-tools

The release target below carries trigger="manual", so OBS never promotes
anything by itself, and a release copies the built binaries rather than
rebuilding them - what reaches users is the exact file that was tested.</description>
  <person userid="pawil" role="bugowner"/>
  <person userid="pawil" role="maintainer"/>
  <build>
    <enable/>
  </build>
  <publish>
    <enable/>
  </publish>
  <debuginfo>
    <enable/>
  </debuginfo>
  <repository name="openSUSE_Tumbleweed">
    <releasetarget project="home:pawil:incus:lts-6.0" repository="openSUSE_Tumbleweed" trigger="manual"/>
    <path project="openSUSE:Factory" repository="snapshot"/>
    <arch>x86_64</arch>
    <arch>aarch64</arch>
  </repository>
  <repository name="openSUSE_Leap_16.0">
    <releasetarget project="home:pawil:incus:lts-6.0" repository="openSUSE_Leap_16.0" trigger="manual"/>
    <path project="openSUSE:Leap:16.0" repository="standard"/>
    <arch>x86_64</arch>
    <arch>aarch64</arch>
  </repository>
</project>

Places

Meta Configuration of home:pawil:incus:lts-6.0:staging

Places