Path: csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod From: Hans-Christoph Steiner Newsgroups: linux.debian.maint.python Subject: Re: GitLab CI on salsa.debian.org Date: Wed, 21 Mar 2018 15:40:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Mar 21 14:30:45 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.701 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -7 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=upBT1t ugl23YIlcw/KzB/JQuu+XdOB6Z6GOiSyDVyOA=; b=eQdOa0/gUV8ciUdze1+Ixr dj1oLDcCAwOA07gW9oGfyhANH73Fn19ddsUpDMv8Z1Q+QQVNSQWMcMg+/SS0Zp7V hZGseCMTLhEhuZnHgaiq/DbHOEiEu63ZrCLdmlVEdlRyUwSdkptCSiw6SrBmzlnx cwyq3eWEKQvNR2Axsom5bjun2kDfgp8GEHflihsb4IGdLUnsANRGuNRoamWPmi6M /S3MSGKyNEOqiavdehHUjrYkYQGwRV5bT24nHy8RK45Pki+q0luEUBlbYJg5grdp ZhYjCAyyxHBG7+FF/FnVsSC9wGI7/PrXp9H9W6+MYZSzJjwgenugDYeTA7bliL5A == X-Me-Sender: Organization: @||@ MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/15689 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/6fab0188-01c6-acf1-f3e0-e96125c7d81c@at.or.at Approved: robomod@news.nic.it Lines: 53 Sender: robomod@news.nic.it X-Original-Date: Wed, 21 Mar 2018 15:27:43 +0100 X-Original-Message-ID: <6fab0188-01c6-acf1-f3e0-e96125c7d81c@at.or.at> X-Original-References: Xref: csiph.com linux.debian.maint.python:10291 Since I got only crickets on this email, let me elaborate: gitlab-ci lets you run whatever you want as root via Docker images. That means its easy to run full builds, installs, and tests in gitlab-ci. It also makes it easy to add CI tests for various releases, like to support backports. .hc Hans-Christoph Steiner: > > One great addition that GitLab gives us is CI builds with custom Docker > images, which will run the whole build/test process for each merge > request. For example: > > https://salsa.debian.org/eighthave/python-vagrant/-/jobs/4005 > > I have set up a prototype Docker image for running git-buildpackage > builds automatically. This Docker image is built and deployed using > Gitlab CI (albeit on gitlab.com): > > https://gitlab.com/eighthave/ci-image-git-buildpackage > > Then any git-buildpackage package can be built by doing this: > > * put git project on salsa > * In Settings -> CI/CD -> General pipelines settings -> > Custom CI config path, set it to: debian/.gitlab-ci.yml > * include debian/.gitlab-ci.yml in the git repo with this contents: > > > > image: registry.gitlab.com/eighthave/ci-image-git-buildpackage:latest > > build: > artifacts: > paths: > - *.deb > expire_in: 1 day > script: > - /gitlab-ci-git-buildpackage > - dpkg -i ../*.deb || apt-get install -f > - mv ../*.deb . > > > > I think we can do a lot of automation in the Docker image, like some of > the stuff I've already done in ci-image-git-buildpackage. If someone > knows how to get ENTRYPOINT and/or CMD working with GitLab CI, then > /gitlab-ci-git-buildpackage could be run automatically. > > .hc >