Deployinator is a deployment framework extracted from Etsy.
We provide simple Continuous Integration for Ruby apps hosted on GitHub. Stop wasting time and money maintaining your own server. In less than two minutes you can go from first login to testing your code.
Here’s what really happens on these teams:
* On day one of sprint #1, someone introduces a bug. They don’t realize it, and it makes it way through the end of the sprint.
* On day one of sprint #2, a stakeholder happens to be playing around with the version of the product that was demoed for sprint #1. She notices the bug, and it’s critical, so she goes to the team lead and asks to have it fixed right away for the PR demo she’s doing on Thursday.
* The team lead and the stakeholder argue about process and deadlines for about an hour.
* The team lead then relents, branches the sprint #1 demo code. He works into the night to fix the bug, test it out, deploy the new version, test it out again, and merge the change into the trunk.
(Link: You’re Already Using Continuous Flow (poorly) – Feedback Junkies)
Welcome to the home of Infinitest, a continuous test runner for JUnit tests. Whenever you make a change, Infinitest runs tests for you. It selects tests intelligently, and only runs the ones you need. It reports unit test failures like compiler errors, and provides additional information that helps you write better tests.
(Link: Infinitest – a continuous test runner for JUnit tests)
Continuous Integration is a fancy term for “run your project’s tests after someone pushes to the repository and notify interested parties if they fail.”
We’re currently in the process of revamping our test suite (which we’ll blog about in the future) and moving servers, so I thought it’d be a good time to re-evaluate our options.
(Link: Continuous Integration Spring Cleaning – GitHub)
A couple of weeks ago, we wrote a post on the “The Ultimate Enterprise Java Build Solution“, to show that nowadays the debate on infrastructure has shifted from open source vs commercial to modular vs integrated. Did we mention that we believe in the modular approach ? I don’t think we did but it was obvious, wasn’t it ? ;-)
The solution described by Christopher Jugg is basically what we have in place to run Nemo, the public instance of Sonar : Maven, Hudson, Nexus, Subversion and Sonar. Here is a diagram that shows our Amazon EC2 infrastructure :
(Link: Hudson Sonar plugin 1.0 : to industrialize the ultimate build system)