61–70 of 79 posts
It's a shame that we are beating a path to another Microsoft monopoly. Have we learned nothing?
When time comes, we will move away from GitHub actions too. What will you have us do, in the mean time? Will you pay to run my open source projects' CI servers? And if you do, what exactly makes you better than "another Microsoft monopoly"?
Earlier quoted context omitted.
When time comes, we will move away from GitHub actions too. What will you have us do, in the mean time? Will you pay to run my open source projects' CI servers? And if you do, what exactly makes you better than "another Microsoft monopoly"?
Why not move to GitLab right now? Their core product is OSS and the CI is integrated and free for OSS projects.
I'm surprised people are still using Travis CI. The writing was on the wall the day of the acquisition. I moved all of my builds immediately.
Also, while I don't imply either to move or to stay, Travis still does the job as it did before¹, so, unless pricing or specific features are a requirement, the technical incentive to move may (may) not be high enough.
¹=I did notice one change though, and it's that the list of the builds slowed down at some point; their solution: reduce the entries listed while loading (!!).
Any recommendations on good open source CI / CDs? Right now I just use github actions, but am interested in other self hosted options.
I know this isn't super helpful, but I built my own bors-style CI bot over a few weekends, and I'm very satisfied with it. It looks for PR comments with a specific keyword, then pulls the branch, tests it, and pushes a merge commit automatically. Taking this approach has two big upsides. First, the bot is just a binary running on a cheap VPS; so I know that it'll be fast and that I can ssh in at any time to debug if…
* A webhook would be fired at my host when a new pull-request was created, or updated.
* When the webhook was received we'd store details of the repository, the branch-name, and the PR-ID into a queue, from the webhook paylad.
* A bunch of worker machines would poll the queue, and when a new message was received they'd checkout the repository, run "make test", and add the output of the run as a comment to the PR.
This was done as a temporary thing, rather than spinning up Jenkins/similar, with the expectation we'd get Github Actions coming to Github Enterprise in the near future.
Earlier quoted context omitted.
sr.ht supports ARM64, PowerPC, and SystemZ from what I can see on the list of supported builds: [0] They also support MIPS (and their BSD builds support SPARC). [0] https://man.sr.ht/builds.sr.ht/compatibility.md
There are no checks in those - they are empty fields.
It's a shame that we are beating a path to another Microsoft monopoly. Have we learned nothing?
When time comes, we will move away from GitHub actions too. What will you have us do, in the mean time? Will you pay to run my open source projects' CI servers? And if you do, what exactly makes you better than "another Microsoft monopoly"?
Earlier quoted context omitted.
Why not move to GitLab right now? Their core product is OSS and the CI is integrated and free for OSS projects.
No free Windows and macOS runners.
I'm surprised people are still using Travis CI. The writing was on the wall the day of the acquisition. I moved all of my builds immediately.
We (radareorg/radare2 team) use Travis CI specifically to build and run tests on ARM64 (ARMv8 or AArch64), PowerPC64, and SystemZ (s390)[1]. No other CI service offers those. I wish there were also MIPS, SPARC, and RISC-V. [1] https://travis-ci.com/github/radareorg/radare2/builds/202966...
Earlier quoted context omitted.
When time comes, we will move away from GitHub actions too. What will you have us do, in the mean time? Will you pay to run my open source projects' CI servers? And if you do, what exactly makes you better than "another Microsoft monopoly"?
Why not move to GitLab right now? Their core product is OSS and the CI is integrated and free for OSS projects.