Skip to content

WIP: d/salsa-ci.yml: Add salsa.debian.org Gitlab-CI integration

Simon McVittie requested to merge wip/smcv/salsa-ci into debian/latest

Is this something we want to be doing across GNOME Team packages?

Options include:

  • Yes
  • Yes, but disable some stages to speed it up (e.g. disable reprotest, or run either build or reprotest or both with DEB_BUILD_OPTIONS=nocheck to speed them up)
  • No

Caveats:

  • If a package in experimental or -backports has (build-)dependencies that are unsatisfiable in the base suite (unstable or the release to which we are backporting), we will have to set:

      variables:
    RELEASE: experimental

    (or buster-backports etc., as appropriate) like I did in

  • If a package in experimental or -backports has (build-)dependencies that are unsatisfiable in the base suite (unstable or the release to which we are backporting), we will have to disable piuparts and autopkgtest until salsa-ci-team/pipeline#58 (piuparts) and an equivalent feature request (autopkgtest) are fixed

  • If a package has (build-)dependencies that are unsatisfiable in unstable, we will have to disable reprotest until salsa-ci-team/pipeline#57 is fixed

See the debian/experimental branch of flatpak for sample code. Everything except setting the RELEASE variable is generic and can be copied into all branches.

/cc @laney @bigon @seb128

Merge request reports