On Mon, 2015-05-18 at 21:57 +0200, Guido Günther wrote:
> On Thu, May 14, 2015 at 11:16:23AM +0200, Tzafrir Cohen wrote:
> > On Wed, May 13, 2015 at 07:14:36PM +0300, Исаев Виталий wrote:
> > > Hello! I'm looking for a convenient wrapper of standard Debian packaging
> > > toolchain in order to automatize the deployment process. We use Ubuntu and
> > > Debian, and the most part of code is written in C++, therefore we need to
> > > compile and build binary debs. Currently our infrastructure consists of:
> > > 
> > > 1. Gitlab;
> > > 2. Isolated build environment inside Docker containers (where we
> > >    usually do `git clone && mk-build-deps && debuild`);
> > 
> > Either:
> > 
> > After a clone:
> > 
> >   gbp buildpackage --git-pbuilder
> > 
> > Or:
> > 
> >   gbp buildpackage --git-builder='sbuild'
> > 
> > (gbp is git-buildpackage)
> 
> One can hook this on top of jenkins using e.g. jenkins-debian-glue or a
> simple generic build job that e.g. invokes mini-dinstall at the end.
> Cheers,
>  -- Guido

Just some extra input:

I've been having fun with gitlab-ci (at least using the unofficial
multi-runner), in a similar manner; though I've been looking to toy with
invoking reprepro in place of mini-dinstall.

Here's an example job script [1] for gitlab-ci/docker that installs
deps, builds in clean environment. You could add in the necessary
commands to sign (if desired), then forward the package to your mirror
and invoke the command to add it to the pool over ssh (or however your
ppa/mirror works).

I am planning to do this for tagged commit builds only, which you can
specify different build jobs for tagged commits via gitlab-ci (not to
imply that you can't with Jenkins). 


References:

[1] https://code.mmogp.com/snippets/4


Best,



-- 
Rik

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to