Tell HN: Travis CI is seemingly compromised (once again)

Re:Tell HN: Travis CI is seemingly compromised (once again) by p0nce on Thursday December 08, 2022 @07:54AM (#33907351)

arm64 is one reason.

[ Parent | on HN ]

Re:Tell HN: Travis CI is seemingly compromised (once again) by lostmsu on Thursday December 08, 2022 @10:32AM (#33908899)

Set a GitHub runner on one of those free Oracle Cloud ARM64 instances.

[ Parent | on HN ]

Re:Tell HN: Travis CI is seemingly compromised (once again) by josteink on Thursday December 08, 2022 @12:33PM (#33910637)

Sure that is doable, but it doesn't quite sound like a OOB solution where you just add a flag to your YAML, or another line to your build-matrix and call it a day.

I've honestly missed this on Github Actions, and hadn't (yet) found a simple enough workaround to bother.

[ Parent | on HN ]

Re:Tell HN: Travis CI is seemingly compromised (once again) by lostmsu on Thursday December 08, 2022 @02:19PM (#33911955)

But it is also set and forget kind of thing.

[ Parent | on HN ]

Re:Tell HN: Travis CI is seemingly compromised (once again) by josteink on Saturday December 10, 2022 @08:51AM (#33932590)

If it’s that easy… git a link to a quick howto? :)

Does it work regular (free) accounts, free organizations or other similar setups used by non-commercial open-source projects?

[ Parent | on HN ]

Re:Tell HN: Travis CI is seemingly compromised (once again) by lostmsu on Saturday December 10, 2022 @11:39AM (#33934019)

https://docs.github.com/en/actions/hosting-your-own-runners/...

You can find a guide on getting an ARM64 instance in Oracle Cloud elsewhere.

[ Parent | on HN ]