If anybody is using this and can share their experience, I would love to hear it. As far as I can tell the only other significant self-hosted CI project is Jenkins, and I'm interested in alternatives.
I think for many keeping source-code locked down is important.
One could argue that i.e. this/Travis/you is better at security then the average software company [it's probably true!]. But I still think many are more comfortable with keeping the source-code under their control.
Doing something like Github Enterprise for a reasonable price shouldn't be too difficult, I'd wager.
> I think for many keeping source-code locked down is important.
This is the primary reason we went with self-hosted bamboo and octopus deploy for CI and deployment. It does move managing the infrastructure of it all over to our side, but it could always be worse, I suppose (previous jobs not having any sort of structured deployment workflow, in particular)
Ditto -- like the other respondent to this comment, our company has avoided solutions like Travis to keep our enterprise software source code closed. CircleCI's breach about a year ago was a little scary...
I didn't post the grandparent, but we have a self-hosted Jenkins instance and have looked as hosted alternatives. One issue is that we use the build artifacts to deploy to developer machines, and those are Macs. So we need the CI setup to build Linux (for live deployment) and Mac binaries. From a quick browse it wasn't clear if circleci can do that.
I use circleci every day. My test suite is pretty big so I run them with 12x parallel and it takes about 5-8 minutes. On peak hour I almost always have failing tests because something on circleci's end segfaults. This is why I'm considering something self-hosted, it's an annoying problem to have to restart tests 1-3 times to get them to pass...
I'm a Strider contributor. One of the things that attracted me to Strider is the ability to self-host and run private builds for free. Strider is easily hosted on Heroku although this can be somewhat limiting if you need additional services for your tests. The architecture is also highly componentized so it's quite easy to hack in support for a new language. When I first added support for Ruby, it took well under an hour.
This site isn't loading for me, but the concept of continuous integration is something that needs more open source tools. Some one should do a survey of all the companies and how close they come to 1 click CI. I'm guessing most people have at least 3 or 4 manual steps in their deployment processes.
Personally I'm pro-strider because self hosting is cheaper than most hosted solutions and its a great way to learn and get started with CD. I think the barrier to starting CD is too high and its mainly a misconception of difficulty. Strider is a great way to just get started; you can even try locally with a simple 'npm install -g strider'
23 comments
[ 4.1 ms ] story [ 56.8 ms ] thread[Disclaimer: I work at https://circleci.com, a competitor]
One could argue that i.e. this/Travis/you is better at security then the average software company [it's probably true!]. But I still think many are more comfortable with keeping the source-code under their control.
Doing something like Github Enterprise for a reasonable price shouldn't be too difficult, I'd wager.
This is the primary reason we went with self-hosted bamboo and octopus deploy for CI and deployment. It does move managing the infrastructure of it all over to our side, but it could always be worse, I suppose (previous jobs not having any sort of structured deployment workflow, in particular)
[0] https://drone.io
http://www.go.cd/
https://news.ycombinator.com/item?id=7646197
[0]: https://buildbox.io/#learn-more
Personally I'm pro-strider because self hosting is cheaper than most hosted solutions and its a great way to learn and get started with CD. I think the barrier to starting CD is too high and its mainly a misconception of difficulty. Strider is a great way to just get started; you can even try locally with a simple 'npm install -g strider'