For discussion of Alpine Linux development and developer support

7 7

[alpine-devel] Change Travis in Alpine Continuous Integration

Roberto Oliveira
Details
Message ID
<8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com>
Sender timestamp
1499730473
DKIM signature
missing
Download raw message
Hi Folks,

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?


Regards,
Roberto Oliveira





---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Timo Teras
Details
Message ID
<20170711161226.2305c649@vostro.util.wtbts.net>
In-Reply-To
<8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com> (view parent)
Sender timestamp
1499778746
DKIM signature
missing
Download raw message
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
---
Roberto Oliveira
Details
Message ID
<09d55b48-b217-dc3e-500e-aa8ed208f484@linux.vnet.ibm.com>
In-Reply-To
<B221CE47-B2FF-43DF-8C74-58966256CA20@jirutka.cz> (view parent)
Sender timestamp
1499804039
DKIM signature
missing
Download raw message
Hi Jakub,

Yes, I was suggesting to use Jenkins instead of Travis to do what Travis 
does now (testing the pull requests).

Travis integrates very well with GitHub but I think Jenkins works nice 
too. Why would you not recommend Jenkins?


Regards,

Roberto Oliveira


On 07/11/2017 04:21 PM, Jakub Jirutka wrote:
> Hi,
>
> we use Travis CI for testing pull requests (and only for that) because it’s free and well integrated with GitHub. Our build infrastructure uses just a simple shell script for running builds, so it’s currently not usable for this use case.
>
> We would like to improve this, use some real CI software, but haven’t found anything suitable yet. I know Jenkins CI and it’s one of the last CI software I would recommend…
>
> Jakub
>
>> On 11. Jul 2017, at 1:47, Roberto Oliveira <rdutra@linux.vnet.ibm.com> wrote:
>>
>> Hi Folks,
>>
>> 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?
>>
>>
>> Regards,
>> Roberto Oliveira
>>
>>
>>
>>
>>
>> ---
>> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
>> Help:         alpine-devel+help@lists.alpinelinux.org
>> ---
>>
>
>
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Jakub Jirutka
Details
Message ID
<B221CE47-B2FF-43DF-8C74-58966256CA20@jirutka.cz>
In-Reply-To
<8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com> (view parent)
Sender timestamp
1499800909
DKIM signature
missing
Download raw message
Hi,

we use Travis CI for testing pull requests (and only for that) because it’s free and well integrated with GitHub. Our build infrastructure uses just a simple shell script for running builds, so it’s currently not usable for this use case.

We would like to improve this, use some real CI software, but haven’t found anything suitable yet. I know Jenkins CI and it’s one of the last CI software I would recommend…

Jakub

> On 11. Jul 2017, at 1:47, Roberto Oliveira <rdutra@linux.vnet.ibm.com> wrote:
> 
> Hi Folks,
> 
> 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?
> 
> 
> Regards,
> Roberto Oliveira
> 
> 
> 
> 
> 
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
> 



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Yves Schumann
Details
Message ID
<ec1cdd9f-b870-b484-1720-697e701f8b3a@eisfair.org>
In-Reply-To
<B221CE47-B2FF-43DF-8C74-58966256CA20@jirutka.cz> (view parent)
Sender timestamp
1499803735
DKIM signature
missing
Download raw message
Hi Jakub

Am 11.07.2017 um 21:21 schrieb Jakub Jirutka:
> We would like to improve this, use some real CI software, but haven’t found anything suitable yet. I know Jenkins CI and it’s one of the last CI software I would recommend…

I'm very interested to know, why you not recommend Jenkins. Which other
CI system do you know and what are their benefits against Jenkins?

Kind regards,
Yves
William Pitcock
Details
Message ID
<CA+T2pCE0eaRoFnhegtsrL_03Gvpra2ertSW2JTGQBo7bKckJ9w@mail.gmail.com>
In-Reply-To
<B221CE47-B2FF-43DF-8C74-58966256CA20@jirutka.cz> (view parent)
Sender timestamp
1499844487
DKIM signature
missing
Download raw message
Hi,

On Tue, Jul 11, 2017 at 2:21 PM, Jakub Jirutka <jakub@jirutka.cz> wrote:
> Hi,
>
> we use Travis CI for testing pull requests (and only for that) because it’s free and well integrated with GitHub. Our build infrastructure uses just a simple shell script for running builds, so it’s currently not usable for this use case.
>
> We would like to improve this, use some real CI software, but haven’t found anything suitable yet. I know Jenkins CI and it’s one of the last CI software I would recommend…

It seems like we could use buildbot and this software:
https://github.com/barosl/homu to handle the Github side of it.

William


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Natanael Copa
Details
Message ID
<20170712125533.4b1e5b63@ncopa-desktop.copa.dup.pw>
In-Reply-To
<8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com> (view parent)
Sender timestamp
1499856933
DKIM signature
missing
Download raw message
On Mon, 10 Jul 2017 20:47:53 -0300
Roberto Oliveira <rdutra@linux.vnet.ibm.com> wrote:

> Hi Folks,
> 
> 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?

I don't know if other tools are better suited (eg buildbot) but I am
all for adding CI for other arches  we can catch arch specific errors
before they enter our git master.

Jenkins is probably not something I would have used myself, but I also
believe that the person doing the job should have liberty to pick the
tools for it too.

Also, if we could get jenkins run on alpine, then it would be a nice
showcase.

-nc


> 
> 
> Regards,
> Roberto Oliveira
> 
> 
> 
> 
> 
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
> 



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Breno Leitao
Details
Message ID
<413b619c-a02c-7b10-6f19-72304f13eba2@br.ibm.com>
In-Reply-To
<8a467904-a94c-fdbb-6817-12f9d32baf4f@linux.vnet.ibm.com> (view parent)
Sender timestamp
1533232572
DKIM signature
missing
Download raw message
Hi there,

On 07/10/2017 08:47 PM, Roberto Oliveira wrote:
> Hi Folks,
> 
> 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.

I am reviving this thread because Travis now has support for ppc64le and
Jenkins might not be required anymore.

It seems Travis on ppc64le does not have trusty, but xenial. And the 'os'
name is "linux-ppc64le".



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---