moritzplassnig

TL;DR: Lighthouse is Prow + support for other git providers like Bitbucket or GitLab

What are good examples?

I assume it happens regularly. I had a couple of flights myself on other plans than initially advertised. I always assumed that the airline canceled/delayed other flights because of it (taking plane a and crew a from flight a to do flight b with plane a).

Before the 737 Max got grounded (after the 2nd crash), I remember reports that some airlines allowed passengers to rebook their flights for free (to end up on a different plane). I doubt they will continue doing it once the 737 Max is allowed to fly again. Eg, Southwest is too dependent on it.

When GitHub's financials got leaked in 2016, GitHub's personal accounts accounted for 12.5% of their revenue. GitHub Enterprise was 50%, their organization (= business) accounts were the remaining 37.5% [1]. It's fair to say that the personal accounts are irrelevant from a revenue perspective.

[1] https://medium.com/@moritzplassnig/github-is-doing-much-bett... (disclaimer: I wrote the article but the data is by Bloomberg)

Out of curiosity (CodeShip founder here), what could we have done better?

Yes, good point. Updated the title.

Sendgrid [1] has better margins than Twilio [2] (75% vs. 54%).

[1] https://www.sec.gov/Archives/edgar/data/1477425/000155837018... [2] https://www.sec.gov/Archives/edgar/data/1447669/000110465918...

And those companies usually took on debt additionally which is more senior than the equity investors.

They likely are doing both, raising $ for % and debt additionally. It's not either or, just that debt rounds usually don't get reported/announced. They often happen hand in hand with investment rounds.

And Splunk bought VictorOps, the third company in that market

10-13x ARR isn't absurdly high at all

We pushed data automatically into a Google Sheet (e.g. importdata() from Looker). The sheet had a column per month and I simply exported that sheet at the end of a month and shared it with our investors (together with an email update). Super easy, the Google Sheet "dashboard" was available to everybody in the company and our investors received the same information.

That would be awesome. Could you email me at mo@codeship.com? I will connect you with the right person.

Thank you :)

Sorry to hear about those issues. I shared your feedback with a couple of people, and we will work hard on being more mindful when making such changes going forward.

If you have more feedback, I'm happy to connect with one of the PMs or somebody from the Jenkins OSS team.

I'm the founder/CEO of Codeship and we got acquired by CloudBees earlier this year. And I want to make sure that Jenkins + all CloudBees products get better :)

Thank you :) Did you have a chance to watch the video on our blog? That addresses some of your questions.

Although we started as a cloud/SaaS platform, we always wanted to serve the whole market. Partnering with CloudBees allows us to do that and together, we can help pretty much any developer or dev team in the world, on-prem or cloud, technology agnostic, etc.

The Codeship brand will continue because we think a lot of people know it and we want to avoid confusing them. I also think it makes sense to have different brands for the cloud/SaaS piece and the on-prem products.

I think that's a good point. There's quite some fragmentation in the cloud CI/CD space (if we look beyond Jenkins). If necessary, GitHub could still acquire down the road. The downside risk is small.

The content will stay online. We don't know yet if it's on the codeship.com or the cloudbees.com domain. Probably primarily an SEO question.

We will also continue to blog and likely do more of that because we will now also start covering a lot of Jenkins topics.

If you have any concerns, please email, tweet, etc. me.

I think the majority of developers & companies doesn't want one product that does everything. It's better for the user to have clear APIs, solve specific problems very well and then make it easier to integrate with other products. It should all be building blocks that work well together. You should be able to use, e.g., GitHub because you prefer it over Bitbucket, integrate it with Codeship (or whatever other CI/CD solution you like) and then add other products like Percy or Code Climate as needed. There's a use case, and some people prefer to get everything out of one hand, but if we look at how software is getting purchased nowadays, it's more and more team-focused, fewer company-wide purchases. That's great. Pick the tools and products that solve your specific problem very well, as long as they integrate well with what the rest of your team uses.

Now that doesn't mean you couldn't build a company that does everything, or that Microsoft couldn't start acquiring and then does everything (they kind of doing it already, same with AWS). What we can see, though, is that the quality of specific products isn't that great. That's not surprising. It's easier to do a few things very well vs. 200 things.

And yes, I'm biased because of Codeship :)

You are right, you never know. I think CloudBees is trying hard to do it the right way and ensure that the result is better products for our customers. That means doubling down on both, Codeship and Jenkins and figure out ways to align the products more (eg. Codeship pipeline configuration and Jenkins pipeline configuration).

Yes. We already had a lot of discussions about that. I know it's not a problem that's easy to solve and it will take some time but I'm excited about tackling it

Codeship founder here: Happy to answer any questions, especially if you are a Codeship user/customer :)

Codeship founder here: Happy to answer any questions, especially if you are a Codeship user/customer :)

I doubt because 500s didn't fulfill their part of the contract.

I wonder if the paperwork (eg. term sheet or whole contract) got signed before Dave McClure left and (some) LPs are holding back their money now. Is that a realistic scenario?

Or it was planned to happen ahead of re:Invent anyway. I think it's fair to assume that there's a big chance that AWS is launching a managed k8s product.

@Mods: Please mark as dead

Codeship founder here. We support .yml file config for our container/Docker based product (called Codeship Pro). We're looking into offering a UI + yml file approach for both products because we see a 50-50 split when it comes to what people prefer. Thanks for the feedback :)

You can find the original study (from the University of Washington) here: http://www.nber.org/papers/w23532

And the UC Berkeley study here: http://irle.berkeley.edu/files/2017/Seattles-Minimum-Wage-Ex...

Does anybody in this thread have more information about Google Hire's pricing? I emailed Google twice, and they weren't willing to share it so far ("attend this webinar to learn more").