Drip is continuous integration for node.js.
Visit and click the run button to watch tests run for a popular node.js library. View builds for other libraries. Setup a post-receive hook to trigger builds from GitHub! Test expresso, whiskey or any framework with a makefile!
socket.io coffee-resque express.js expresso mongohq redistogo mongoose backbone.js jade
Voting is now closed.









































(42)
AnkurBulsara
okaysamuraiInteresting idea, seems limited in use but what it does it seems to do well. Nice use of colors/icons to help read the information a little better. Good idea to brand it, makes it more interesting than many other code-based entries. Nice work! | |||
Nice! A great little bit of kit, loved the integration directly into github (forced me to make one my libraries' testsuites work with it, which was useful for me as well!) Clearly there are lots of test-runners out there, but this has a nice clean design and really good integration loved the fact it ‘just worked’ even when it had to do complex compilations and all sorts of mess! I put the wrong url in a few times so would be nice to be able to remove repositories too, but other than that a great entry :) | |||
hunedhm, it didn’t work. but useful idea. | |||
Thanks for the vote — what kind of problems are you experiencing?
It’s useful, it looks good, and it’s an overall well put together experience end to end. I had the repositories fail to load a few times, but nothing I’d dock it permanently for; NKO proves high load. ;) | |||
Indeed it does. Anything you’d like to see added? Thanks again for the vote!
Thanks for the vote — any features you’d like to see added?
therazorbladeThis is an interesting idea but doesn’t have a lot of features and adding a new project doesn’t display any confirmation (e.g. UX is simple but not intuitive). | |||
We’ve got lot of new features ready for the next release! What else would you like to see? The UX was much more intuitive before the list of repos was so long; we didn’t realize a confirmation would be so useful until we got so popular! Thanks for the vote!
therazorbladeGlad to hear you will be continuing it. Mostly it needs to clarify what it is doing and looking for. Are you going to allow local installs? Added an innovation star.
Yes, we will. It will be open source, under the MIT license.
kiranryaliVery cool. I love the simplistic design, you guys god a lot achieved pretty quickly. | |||
Thanks for the vote kiran! Let us know if you have any feature requests!
I saw this last night so I know what it looks like an how it functions. I thought it was fairly awesome. fixed All-in-all, I’d definitely use this. | |||
ncb000gt, thanks for the vote. We ran into some load-related issues on our linode when we first launched, but things have stabilized now. Thanks again for sticking with us! Let us know if there’s any questions we can answer!
Ok I can now see it though I updated my repository and haven’t seen the tests run.
What is the update period? Also, which testing frameworks do you support?
Actually I noticed it runs test from a makefile, but I still haven’t noticed it update (pull the latest change set).
Updating the build output? That should be every two seconds.
I just added the push hook and it seems to be working nicely. Ultimately I’d prefer it worked with npm right out, but it seems to be doing what you are advertising. So, editing my score. :)
Thanks a lot :)
Thanks! We’ll release npm support after the judging period is over.
New feature requests (since I haven’t found another way to get in touch): * Which version of node are you running (my C++ module has different code paths). * When did you run the tests. I can find this by traversing my commit tree, but I’d rather not have to. * Somehow distinguish which branch tests were run from in the UI other than “Build output for branch: GH-31” since that shows up as the latest build. I want to see latest for <branch>.
Anyway, not sure if those are helpful or useful, but figured I’d throw them in here anyway. Thanks!
nymDidn’t work for me, although could be a compelling product with more work ironing out the bugs. | |||
We’re very sorry to hear that nym, what sort of issue did you encounter? It definitely appears to be working for me right now, so hope we can help resolve your issue. Thanks for the vote!
Thanks a lot for your vote! Is there any questions we can answer or features you’d like to see added?
I tried to use it, but nothing happened. | |||
Thanks for the vote!
Were you having running builds, or loading the page?
Clicking on run em' took me to the add page, but nothing happened at all. I bet your poor hosting instance is being hammered. I’m revising my utility vote since It works, just not for me.
jerrysievertwould have been nice if the package.json could be read and the test methodology, or ran npm test. | |||
Agreed on both accounts. We aimed to have more integration than we could fit into the time allotted. We started with visionmedia’s repos which were mostly expresso with Makefiles. We’re currently working on expanding the supported frameworks and will be releasing updates after the judging period.
Thanks for your vote!
mranneyI’m glad to see the state of node-based CI systems advancing. This is a very nice looking entry. | |||
Thank you very much! Would love to hear about any features you’d like to see or questions you have!
mdeNice dashboard, very easy on the eyes. | |||
Thanks so much for the vote! Are there any features you’d like to see added or questions we can answer for you?
ryanspoonThank you for your vote! Are there any questions we can answer or features you’d like to see added?
Thanks for the vote! Are there any questions I can answer or features you’d like to see added?
mahemoffVery useful tool. Could do with some more info on exactly what it does and what requirements there are on projects. | |||
Agreed. In hindsight, we should have a page that shows which testing frameworks we support, and how to setup your code so that it’s able to be tested using our service. We’re going to take care of that when we redeploy after the judging period is over.
Thank you very much for your vote!
Thanks a lot for the vote! Let us know if you have any questions or if you’d like to see any features added!
Thanks for your vote! Let us know if you have any questions or would like to see anything changed or added.
Excellent, most excellent. However, I would like to see the server be able to run specified test scripts or files, rather than forcing the use of a Makefile. | |||
We would too. Unfortunately we weren’t able to fit it in during the 48-hours but have been busy adding support for it which will be released post-judging.
Thanks for your vote!
fixed! | |||
Can you take a snapshot of the page? I’m seeing a long list of repos when I hit: http://drip.io/#/repositories . Thank you!
Awesome, thank you!
I like the idea and the site looks nice, but when I try to run the build it doesn’t give any sign it’s working. | |||
Hi juliogreff,
Are you still experiencing these issues?
Thanks, Chris
Well designed, testing is super important! :) Almost complete! | |||
Thank you very much for your vote! Feel free to email/tweet me with any questions you may have.
Been using it heaps over the last couple of days. The post receive hooks are fantastic and it’s an awesomely usable solution. Even though on the first day I noticed it being a little unresponsive I haven’t seen a hiccup since. Revising vote to reflect how damn useful this is to me… | |||
Hey DamonOehlman!
Thanks for the vote — I’m so glad that you’ve found our service so useful! We’ll roll out some updates as soon as the judging period is over! Feel free to email/tweet me with any questions you may have!
Chris
Looks very nice. A loading indicator would be helpful, although completely understandable that one wouldn’t be included given the timespan I almost thought it wasn’t working. I also honestly have no idea what continuous integration is :) | |||
While not a very innovative idea, it’s still great to see that people care about TDD enough to make a test-running server. The fact that it’s easy to use and is easy on the eyes is a major plus. | |||
Could not get it to work, however the design and aesthetic was very good.
In concept, this could be interesting, especially as a cloud-based SAAS platform for continuous integration for NodeJS projects.