maybe they wouldn't have been laid off if they took themselves and their work more seriously? I mean honestly, looking at the team page at https://about.travis-ci.com/team/ , we have titles such as Mermaid on board, Tyranjasaurus Specs, Tortilla Builder, Sausage Dog Wrangler, Customer Avocado, Head Catwoman, and Conjurer of Avocado Patronuses
I think the childish names are artifact of the immaturity of the codebro culture overall. I realize that's not a popular opinion. Not everything has to emulate the old-fashioned, Buttoned-Down, "3-piece business suit + briefcase" IBM Circa 1972, but the silliness that passes for modern IT has gone much too far the other way, IMO. I think it's an insight into the mentality of the builders, and it doesn't speak well fo…
Travis CI Is Laying Off Senior Engineer Staff
91–100 of 105 posts
Re: Travis CI Is Laying Off Senior Engineer Staff
#92Earlier quoted context omitted.
In what sane business is 50$ a month over a free tier the deciding factor in choosing a CI system?
Most (?) developers can't even buy a mouse without prior permission. "Free" is more convient at work than at home. If I need something at home I just pay. At work ... Compare the hazzle of getting a Win10 VM up and running compared to a Ubuntu one with licensing issues. A Win10 image is like 3 days away. An Ubuntu 30 min. The slower alternative also happens to cost money.
You let all of the employees use something for free, come to rely on it, and then all of a sudden it's become entrenched in the workflow/culture/whatever. At that point, it's easier to just pay for the service than to switch.
See Slack.
Re: Travis CI Is Laying Off Senior Engineer Staff
#93I've been using travis Enterprise for over two years and what has kept that going has been the amazing support and development team at Travis who have always helped us during an emergency, been very responsive and informative in all our interactions. They are the reasons I have backlogged the project to migrate. Keys issues i've seen in our Enterprise install... * Upgrades can go bad, very quickly and very silently.…
We’re migrating to in-house Jenkins now. Can’t trust third parties to handle critical infra.
I was a big pusher for Travis, but they’ve lost my trust.
I would advice everyone else to migrate off and mitigate their risk.
Re: Travis CI Is Laying Off Senior Engineer Staff
#94Earlier quoted context omitted.
There's an open todo ticket to add a public pricing breakdown - right now you only see it after signup. This is what the page looks like: https://sr.ht/lS5M.png I'll see if I can't get public pricing info up later today. >Does it require a repo hosted on sourehut too, or can the CI be used independently? You can use the CI independently. Right now there's a GitHub integration and I'm open to adding more :)
Update: pricing page is now shown here: https://sourcehut.org/pricing/
Re: Travis CI Is Laying Off Senior Engineer Staff
#95Earlier quoted context omitted.
Update: pricing page is now shown here: https://sourcehut.org/pricing/
It's not clear from that page what I'm getting for my money.
Or did you feel that this isn't helpful either?
Re: Travis CI Is Laying Off Senior Engineer Staff
#96Whelp, I might be looking at CircleCI vs TravisCI again.
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
#97Earlier quoted context omitted.
It's not clear from that page what I'm getting for my money.
You generally wouldn't go directly here. You'd start at the link I originally posted: https://sourcehut.org/ Or did you feel that this isn't helpful either?
Re: Travis CI Is Laying Off Senior Engineer Staff
#98From the tweet [0] it seems there is going to be a huge tech debt. I don't know how Idera is planning to expand upon the acquisition after letting go people like this. > Some know the skinny on dozens of different open source projects and ecosystems, others understand run time and dep mgmt for like 17 languages and even more tooling, and automated image mastering to handle it all. > Others are rewriting what it means…
To (sadly) be fair, Travis has already been struggling mightily with tech debt the last few years. There have been a lot of issues surface and re-surface that sure seem like they shouldn't be a big deal. For example, setting a build to use ruby 2.4 is supposed to run the latest ruby 2.4.x, but would frequently build against ancient, unsupported rubies for a while, before being silently fixed.
Re: Travis CI Is Laying Off Senior Engineer Staff
#99Earlier quoted context omitted.
This is nonsense; Travis employees are the polar opposite of "codebros". Lighthearted team profiles are absolutely not an insight into the employees' "mentality". If anything, your insinuations are in extremely bad faith and you should know better than to slander people you don't know, especially those whose livelihoods got snatched away. Very lazy and bad stereotyping, 0/10 points, try again.
So why bother having a team page then? If want to contact someone in sales, do I go for the mermaid or the avocado? A technical question, the hot dog or the tortilla? So the only purpose of that page seems to be to prove that the company employs actual humans? As opposed to all those AI run software companies? I know, I'll use the contacts page. If there was any. Which there isn't. Just a twitter handle at the footer…
https://docs.travis-ci.com/imprint.html
Unfortunately, the German word "Impressum" doesn't translate well.
Re: Travis CI Is Laying Off Senior Engineer Staff
#100Earlier quoted context omitted.
Only for open source repo's. For those who have to choose a CI for business use that may not be usable.
In what sane business is 50$ a month over a free tier the deciding factor in choosing a CI system?