You don't want to run unit tests in production and you're using TravisCI? Are you crazy?

  • 0
    What’s wrong with Travis ?
  • 0
    @practiseSafeHex Always down, slow, can't cancel a build, uses tons of non-standard configs.

    Sure it's free but there are far better CI solutions...
  • 1
    @NGPixel we have an paid enterprise copy in work shared across a few thousand people and it ain’t slow for us, think your expecting a little too much out of the free version.

    I could be wrong as I haven’t needed too often, but I’m 99.999% sure I cancelled at least 1 build last year.

    I don’t understand your config comment, all my scripts are just running the default node.js and cloud foundry configs and scripts. Nothing non-standard in any of my 30 - 40 build and deploys.

    Their are probably better, but I’ve only ever used one like Jenkins before where you have to set it up yourself, I much much much prefer the cloud based Travis approach, no issue using it in work.
  • 0
    @practiseSafeHex We are using paid Travis as well, with multiple builds running simultaneously all day long. So I do know what I'm talking about.

    The amount of downtimes or slowdowns we had in the past year is ridiculously high.

    The cancel button is a joke. Have you ever tried it? It says "Cancelling build...." for hours and then gets stuck in limbo state.

    The configs used by Travis for services like MySQL are completely non-standard and don't reflect a default config you would have in a production environment. I had several builds passing tests on Travis but crashing on prod because the database setup was allowing things it shouldn't.

    Jenkins isn't the only solution (it sucks). Take a look at VSTS, CircleCI, Wercker, etc.
Add Comment