On Fri, 18 May 2018 21:15:35 +0200
Philipp Kern <[email protected]> wrote:
> I suppose the test harness is autopkgtest? Is there prior art on how to
> set that up on Salsa? (Picking the backend and making sure that it
> works, for instance.)
Usually I just put debian/.gitlab-ci.yml as below, build package and
kick autopkgtest automatically.
---------------------------------------------------------------------
image: debian:sid
variables:
# adjust to your source package
PKG: screenfetch
stages:
- build
- autopkgtest
package_build:
stage: build
script:
- echo "deb-src http://deb.debian.org/debian sid main" >>
/etc/apt/sources.list && apt update -qq && apt build-dep ./ -y -qq
- apt install -y -qq dpkg-dev && dpkg-buildpackage -us -uc -b && mkdir
build; cd ../; ls -al && mv ./${PKG}_*.deb ./${PKG}_*.changes ${PKG}/build/
artifacts:
paths:
- build/*.deb
- build/*.changes
#piuparts:
# stage: piuparts
# script:
# - apt update -qq && apt install -y -qq piuparts
# - piuparts --mirror=http://deb.debian.org/debian --logfile=../piuparts.log
--fail-on-broken-symlinks build/*.changes
# dependencies:
# - package_build
autopkgtest:
stage: autopkgtest
script:
- apt update -qq && apt install -y -qq autopkgtest
- autopkgtest build/*.changes -- null
dependencies:
- package_build
