Subject: [alpine-devel] Change Travis in Alpine Continuous Integration

From: Roberto Oliveira <[email-masked]>
Date: Mon, 10 Jul 2017 20:47:53 -0300

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:  [email-masked]
Help:         [email-masked]
---

---

From: Breno Leitao <[email-masked]>
Date: Thu, 2 Aug 2018 14:56:12 -0300

Hi there,

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

---

---

From: Jakub Jirutka <[email-masked]>
Date: Tue, 11 Jul 2017 21:21:49 +0200

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 <[email-masked]> 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.
> 

---

---

From: Yves Schumann <[email-masked]>
Date: Tue, 11 Jul 2017 22:08:55 +0200

Hi Jakub

> 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

---

From: Roberto Oliveira <[email-masked]>
Date: Tue, 11 Jul 2017 17:13:59 -0300

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

---

---

From: William Pitcock <[email-masked]>
Date: Wed, 12 Jul 2017 02:28:07 -0500

Hi,

> 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

---

---

From: Timo Teras <[email-masked]>
Date: Tue, 11 Jul 2017 16:12:26 +0300

Hi,

On Mon, 10 Jul 2017 20:47:53 -0300
Roberto Oliveira <[email-masked]> 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.
> 
> machines of different architectures allowing packages to be built in
> the architectures we need.
> 

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

---

---

From: Natanael Copa <[email-masked]>
Date: Wed, 12 Jul 2017 12:55:33 +0200

> 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

---