Earlier quoted context omitted.
>do the minimum with these CI integrations to get my shell script to run This. 100%. Where I'm working is migrating from Bamboo to Jenkins. For my team the new process is just calling "./build-test $params" while others are stuck re-implementing various stages, tasks and blah blah blah. Also an added bonus to this is having the full history of changes to the CI/CD process tracked in git.
I call mine make.sh. Now get off my lawn!
Travis CI's new pricing plan threw a wrench in my open source works
61–70 of 148 posts
Re: Travis CI's new pricing plan threw a wrench in my open source works
#62While I have some sympathy. I also think that expecting travis-ci to effectively donate hours and hours of CPU time a month to endlessly run tests on hundreds on minor projects from one guy is exactly why this change happened. It's unsustainable.
Far from a bad actor just utilizing CPU time for pet projects, Jeff's code is probably in use in a large majority of companies that use Ansible, mine included.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#63Earlier quoted context omitted.
"that's probably not the end goal anymore, just milking the current paying clients and maintaining the status quo." Yep, that's private equity. I won't forget it again. If it makes less and less profit every year even that's probably fine, eventually they'll shut it down, as long as they made back a multiple of what they paid by that point, then it was a good investment. It's sad to me just as an engineer, that travi…
Yes, private equity hates recurring profits. Obviously.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#64While I have some sympathy. I also think that expecting travis-ci to effectively donate hours and hours of CPU time a month to endlessly run tests on hundreds on minor projects from one guy is exactly why this change happened. It's unsustainable.
This "one guy," if you will, is responsible for a majority of the ansible galaxy modules that are out there. Far from a bad actor just utilizing CPU time for pet projects, Jeff's code is probably in use in a large majority of companies that use Ansible, mine included.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#65Earlier quoted context omitted.
I've used it in the past, but when they finally killed off the 1.0 builders (?) my company went to an "internally" hosted Jenkins[1] server and I haven't played with any of the 2.0 stuff. Have you? How do you find working with it? [1] I did also ask about selfhosted stuff, but I'm not willing to host Jenkins for myself. I've heard nothing but complaints about managing a Jenkins install. It's been fine as a user (if a…
Not the person you're asking, but we use CircleCI, and it's fine. The YAML config language is okay, it gets the job done and hasn't been horrible to maintain or modify. Though we only have a few steps in each. My current gripe is that there doesn't seem to be any way to declare that one pipeline depends on another, though I may just be missing something in the docs. What I'm trying to do is have my front-end feature…
Re: Travis CI's new pricing plan threw a wrench in my open source works
#66Hey Jeff, This is hitting me hard, too. I hope this is the right moment for me to pipe up and say this: I always just do the minimum with these CI integrations to get my shell script to run. I am grateful for the free minutes they offer open source projects - but any of the deeper integrations, the advanced automation? No, thanks. It's not like the other developers who use what I write have any more motivation than I…
>do the minimum with these CI integrations to get my shell script to run This. 100%. Where I'm working is migrating from Bamboo to Jenkins. For my team the new process is just calling "./build-test $params" while others are stuck re-implementing various stages, tasks and blah blah blah. Also an added bonus to this is having the full history of changes to the CI/CD process tracked in git.
Re: Travis CI's new pricing plan threw a wrench in my open source works
#67Earlier quoted context omitted.
This "one guy," if you will, is responsible for a majority of the ansible galaxy modules that are out there. Far from a bad actor just utilizing CPU time for pet projects, Jeff's code is probably in use in a large majority of companies that use Ansible, mine included.
How much money does your company contribute to Jeff?
Re: Travis CI's new pricing plan threw a wrench in my open source works
#68Hey Jeff, This is hitting me hard, too. I hope this is the right moment for me to pipe up and say this: I always just do the minimum with these CI integrations to get my shell script to run. I am grateful for the free minutes they offer open source projects - but any of the deeper integrations, the advanced automation? No, thanks. It's not like the other developers who use what I write have any more motivation than I…
Re: Travis CI's new pricing plan threw a wrench in my open source works
#69The HN thread from when Travis's purchase by Idera (private equity) was announced, Jan 2019: https://news.ycombinator.com/item?id=18978251 I had pretty much already learned that "bought by private equity" means "run away as fast as you can, they are going to gut it", and I suspected as much from the travis purchase... but I didn't take action, hoping it would not be true, and not wanting the work of moving projects a…
https://news.ycombinator.com/item?id=19218036
That's when I started recommending clients make plans to move to another provider