Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Date: Tue, 11 Jul 2017 16:12:26 +0300
From: Timo Teras <timo.teras@iki.fi>
To: Roberto Oliveira <rdutra@linux.vnet.ibm.com>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Change Travis in Alpine Continuous Integration
Message-ID: <20170711161226.2305c649@vostro.util.wtbts.net>
In-Reply-To: <8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com>
References: <8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

On Mon, 10 Jul 2017 20:47:53 -0300
Roberto Oliveira <rdutra@linux.vnet.ibm.com> wrote:

> Alpine CI currently uses Travis to build packages when a pull request
> is opened. However Travis only support x86_64 and it just build the
> changes in this architecture.
> 
> Jenkins currently have support for more architectures and we could
> use it instead of Travis. Jenkins has a plugin called "GitHub pull
> request builder" that allows to listen when a pull request is opened
> in GitHub and build with the changes.
> 
> We could install Jenkins in a machine and create nodes for other 
> machines of different architectures allowing packages to be built in
> the architectures we need.
> 
> What do you think about using using Jenkins instead of Travis?

Support for testing on more architectures is something we want.

We are also looking at buildbot currently. This would be to replace the
official builder LXC hosts with buildbot running the build job in
chroot. The recent 'abuild rootbld' commits are for this purpose.

Ideally our official builders could do the CI for GitHub and
PatchWorks, but that's still a way to go. Perhaps Jenkins could be
interim solution? Or you think we should concentrate to get the buildbot
setup up and running?

/Timo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---