Which architectures to support in a CI like Travis?

[Mats Wichmann]

On 9/18/22 03:46, c.buhtz at posteo.jp wrote:
> Hello,
> 
> I am using TravisCI for my project on GitHub. The project is packaged
> for Debian, Ubuntu, Arch and several other distros.
> 
> All this distros support multiple architectures and they have their own
> test machines to take care that all packages working on all archs.
> 
> On my side (upstream) I wonder which arch I should "support" in my
> TravisCI configuration. I wan't to speed up travis and I want to save
> energy and carbon.
> 
> I suspect that my Python code should run on much every platform that
> offers a Python interpreter. Of course there are edge cases. But they
> would be captured by the distros own test environments.
> 
> So is there a good and objective reason to support multiple (and maybe)
> exotic platforms in a CI pipeline on upstream?
> 
> Kind
> Christian

Kind of unrelated to the actual question, but if you start doing 
anything serious under Travis you'll run out of free minutes rather 
quickly.  My project had to just give up on it after they changed their 
licensing models....