Stop Breaking the Build

Cap'n Grumpy writes "You know the score - you've just finished some coding, do a final cvs update before commiting, and all of a sudden all hell breaks loose. Your code now refuses to compile, or xunit starts flashing up red - test failures! One of the other members of your team has checked in something which breaks the build, and they just went out for lunch ... Argh! Did you know there is a solution to this problem? It is a system which makes it impossible for people to check in code which does not compile or test successfully. It allows coders to review others coding efforts code before it goes into the baseline, rather than after. It organises your checkins into logical change sets. It enforces continuous integration. It is linux based, and GPL'd. It's called Aegis."

Comments

Re:Doesn't work on Windows

[ObviousGuy]

Say what you will about the importance of Unix systems, but it doesn't change the fundamental fact that most medium to large-scale programs are written for Windows computers.

Unix programs are very specialized, filling niches that require high levels of stability. Therefore you see Unix used as the core of large business running only a handful of programs (server software, database software, etc). Once a Unix system is running smoothly, there is only a need to maintain the exisitng software, not buy or write new software.

Windows, on the other hand, is everywhere. Everyone uses it (except for a few OS bigots) and that creates a market for new programs. Which brings us back to the original point, which isn't that Unix systems only make up a fraction of the total amount of software, but that it would be interesting to know about a system like Aegis that worked on Windows.

Nothing against Unix at all. It's a nice OS for some things.