7 ms·

CloudBees acquires Codeship as devops consolidates

128 points by moritzplassnig 9y ago

mooreds 9y ago
Here's the announcement from codeship: https://blog.codeship.com/codeship-acquired-by-cloudbees/ https://blog.codeship.com/codeship-acquired-by-cloudbees/
moritzplassnig 9y ago
Codeship founder here: Happy to answer any questions, especially if you are a Codeship user/customer :)
- oblio 9y ago
  I imagine that you have quite a good UI/UX team, considering your company's focus. Will some of them contribute to Jenkins? It badly needs a revamp, and not only for the pipelines/Blue Ocean :)
  - moritzplassnig 9y ago
    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
    - deleted 9y ago
      [deleted]
- tauntz 9y ago
  Former greenhouseci.com founder/CEO and also a Seedcamp alumni here. I know how though the market can be - congrats! :)
- wouterinho 9y ago
  Congratulations! I hope the product continues to be here in the future. The blogpost seems to be reassuring, but with acquisitions you never know.
  - moritzplassnig 9y ago
    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).
    - bryanlarsen 9y ago
      Yah, that would be pretty awesome if codeship could read Jenkinsfile and/or vice versa.
- kavok 9y ago
  Congrats! I've used codeship for awhile now. Was sad to see the live chat/help go.
  - mlocher 9y ago
    Hey there, live chat is still available on some of the pages. Could you let me know where you're missing it? That said, we try to get most support requests via https://helpdesk.codeship.com https://helpdesk.codeship.com (or the widget shown in app), since complex technical problems are usually not that easy to resolve using a live chat tool.
- nickstinemates 9y ago
  Congrats!
- pselbert 9y ago
  Is there a long term plan for the Codeship domain, blog, and the content that you've generated? I ask this because I've written content for the Codeship blog before and have links to it from my personal blog. If the content is going to vanish I'd like to publish it directly rather than have it lost to the ether.
  - brightball 9y ago
    I’m interested in this exact question. :)
  - moritzplassnig 9y ago
    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.
  - manualwise 9y ago
    Hi! Manny here. It certainly won't be lost. We'll let our blog contributors next steps once they are defined! We'll certainly continue publishing articles.
  - jlgaddis 9y ago
    Having seen this before firsthand (even when told it wasn't going away), I'd recommend you take a few moments to make copies of anything you might want in the future.
hkarthik 9y ago
I'm surprised we haven't seen more consolidation of companies whose primary product is related to developer experience. I always thought either Github or Microsoft would start snatching up all these small companies to integrate them more tightly to sell as end to end packages. Anyone in this space have any insight into why that hasn't happened yet?
- pm90 9y ago
  GitLab has been doing an excellent work of integrating CI/CD tools with their code hosting solution; I'm guessing thats what you're talking about. Specifically for Github, I believe they want to focus on hosting and developing (reviewing and managing) code and not on owning the CI/CD tools. They do provide many many integrations with different tools (TravisCI, Jenkins etc.). Which is a good thing: I want Github to be working on making code development better and remain agnostic of pipeline tools, which come and go as fashion dictates (OK I'm being a little harsh but my point is that I should be able to choose my CI/CD tools while having all my code live in Github).
  - colbyh 9y ago
    It would benefit Github to own a CI/CD tool if said tool was used in the vast majority of projects and there was little worry about disrupting the rest. E.g. if Codeship was used by 99% of Github customers it would totally make sense for them to purchase the co and integrate more tightly. But since the pipeline space is varied and rich, as you say, they benefit quite a bit by being a centralized tool that connects to all of them. Just pointing out that should that change in the future (in some unrelated area, say code review as a service?) we could very well see GH plop down a ton of cash and break out of that "code development tools" vertical.
    - moritzplassnig 9y ago
      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.

Here's the announcement from codeship: https://blog.codeship.com/codeship-acquired-by-cloudbees/ https://blog.codeship.com/codeship-acquired-by-cloudbees/

moritzplassnig 9y ago

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

oblio 9y ago
I imagine that you have quite a good UI/UX team, considering your company's focus. Will some of them contribute to Jenkins? It badly needs a revamp, and not only for the pipelines/Blue Ocean :)
- moritzplassnig 9y ago
  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
  - deleted 9y ago
    [deleted]
tauntz 9y ago
Former greenhouseci.com founder/CEO and also a Seedcamp alumni here. I know how though the market can be - congrats! :)
wouterinho 9y ago
Congratulations! I hope the product continues to be here in the future. The blogpost seems to be reassuring, but with acquisitions you never know.
- moritzplassnig 9y ago
  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).
  - bryanlarsen 9y ago
    Yah, that would be pretty awesome if codeship could read Jenkinsfile and/or vice versa.
kavok 9y ago
Congrats! I've used codeship for awhile now. Was sad to see the live chat/help go.
- mlocher 9y ago
  Hey there, live chat is still available on some of the pages. Could you let me know where you're missing it? That said, we try to get most support requests via https://helpdesk.codeship.com https://helpdesk.codeship.com (or the widget shown in app), since complex technical problems are usually not that easy to resolve using a live chat tool.
nickstinemates 9y ago
Congrats!
pselbert 9y ago
Is there a long term plan for the Codeship domain, blog, and the content that you've generated? I ask this because I've written content for the Codeship blog before and have links to it from my personal blog. If the content is going to vanish I'd like to publish it directly rather than have it lost to the ether.
- brightball 9y ago
  I’m interested in this exact question. :)
- moritzplassnig 9y ago
  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.
- manualwise 9y ago
  Hi! Manny here. It certainly won't be lost. We'll let our blog contributors next steps once they are defined! We'll certainly continue publishing articles.
- jlgaddis 9y ago
  Having seen this before firsthand (even when told it wasn't going away), I'd recommend you take a few moments to make copies of anything you might want in the future.

hkarthik 9y ago

I'm surprised we haven't seen more consolidation of companies whose primary product is related to developer experience. I always thought either Github or Microsoft would start snatching up all these small companies to integrate them more tightly to sell as end to end packages. Anyone in this space have any insight into why that hasn't happened yet?

pm90 9y ago
GitLab has been doing an excellent work of integrating CI/CD tools with their code hosting solution; I'm guessing thats what you're talking about. Specifically for Github, I believe they want to focus on hosting and developing (reviewing and managing) code and not on owning the CI/CD tools. They do provide many many integrations with different tools (TravisCI, Jenkins etc.). Which is a good thing: I want Github to be working on making code development better and remain agnostic of pipeline tools, which come and go as fashion dictates (OK I'm being a little harsh but my point is that I should be able to choose my CI/CD tools while having all my code live in Github).
- colbyh 9y ago
  It would benefit Github to own a CI/CD tool if said tool was used in the vast majority of projects and there was little worry about disrupting the rest. E.g. if Codeship was used by 99% of Github customers it would totally make sense for them to purchase the co and integrate more tightly. But since the pipeline space is varied and rich, as you say, they benefit quite a bit by being a centralized tool that connects to all of them. Just pointing out that should that change in the future (in some unrelated area, say code review as a service?) we could very well see GH plop down a ton of cash and break out of that "code development tools" vertical.
  - moritzplassnig 9y ago
    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.