Date: Tue, 18 Sep 2018 22:27:44 -0400
From: Drew DeVault <sir@cmpwn.com>
To: Michael Wyraz <michael@wyraz.de>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Proposal: Multi-Arch matrix builds on travis-ci
Message-ID: <20180919022743.GA12449@homura.localdomain>
References: <c35bd4f4-5a3a-dc22-a808-4158925e6565@wyraz.de>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c35bd4f4-5a3a-dc22-a808-4158925e6565@wyraz.de>

Throwing my hat in the court... I've been talking here about my service,
builds.sr.ht, which may be better suited to this than Travis CI, in this
thread:

https://bugs.alpinelinux.org/issues/9134

In summary, it should also be able to support multi-arch builds, though
I still need to build that out. It should be nearly trivial, I can
prioritize it if you folks are interested in using it. Advantages over
Travis:

- First-class KVM support
- First-class Alpine support, no need to hack up Ubuntu
- builds.sr.ht is 100% FLOSS (BSD and AGPL)

I've also purchased some RISC-V hardware, with which I will be porting
Alpine to riscv64 (when it arrives, probably in November) using
builds.sr.ht. I also use it to build packages for my third-party Alpine
repo, here are some examples:

https://builds.sr.ht/~sircmpwn/job/7545
https://builds.sr.ht/~sircmpwn/job/7553
https://builds.sr.ht/~sircmpwn/job/7552

It can also integrate with GitHub and mailing lists. In addition to
QA'ing GitHub PRs and alpine-aports emails, it can also be leveraged to
help Alpine developers automate publishing new versions of the package
to the official repos.

Happy to share accounts on my instance with any interested Alpine
developers or users.


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---