News for hackers. Stuff that matters.
Re:Travis CI Is Laying Off Senior Engineer Staff by eeeeeeeeeeeee on Thursday February 21, 2019 @01:40PM (#19219351)
You should have already been doing this, before the acquisition. It felt like Travis had been on auto-pilot for a long time. It was painfully obvious to me and our team that Circle is actually hungry and constantly innovating and wanted our business. We moved one project to Circle, waited a bit, and then moved everything away from Travis. Don't regret it one bit.
Re:Travis CI Is Laying Off Senior Engineer Staff by urda on Thursday February 21, 2019 @02:26PM (#19219772)
Hard to want to keep updating your working CI solution for your open source stuff while holding down a job and life and everything else. :)
Re:Travis CI Is Laying Off Senior Engineer Staff by bd82 on Thursday February 21, 2019 @06:05PM (#19221489)
I kept putting of switching from Travis to Circle-CI in one of my open source projects, But when I did get around to it the whole thing went pretty smoothly and easily and I regret not doing it earlier.

1.The builds are much faster now. 2. The configuration has virtually no hacks anymore as I'm using Circle-CI own docker images (including browsers). 3. And the UI/UX is superior as well.

Re:Travis CI Is Laying Off Senior Engineer Staff by eeeeeeeeeeeee on Thursday February 21, 2019 @04:43PM (#19220837)
Hah agreed :) We had one project that kept breaking in Travis, and we started to realize that starting over in Circle was easier than the troubleshooting / feedback loop in Travis.
Re:Travis CI Is Laying Off Senior Engineer Staff by Rapzid on Thursday February 21, 2019 @11:38PM (#19223180)
I got stuck as soon as I found out CircleCI didn't scrub secrets from the log automatically like TravisCI. I know, I know, but we have a pretty hefty legacy OSS build in place and that's a lot to shore up before go time haha. Need to check back on that feature request...