Slashdot Mirror

← Back to Stories (view on slashdot.org)

Stop Breaking the Build

Posted by chrisd on from the perforce-not-subverting-cvs dept.

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."

5 of 92 comments (clear)

  1. Other ideas... by Pentagon13 · · Score: 3, Funny
    Some more ways to improve the checkin process:

    run the code through a lameness filter before allowing the check-in

    enforce a 20 second delay from the time you want to check-in to the time you are actually allowed to check-in

    make sure a different developer checks-in the exact same code a day or two later

    1. Re:Other ideas... by Anonymous Coward · · Score: 2, Funny

      Please try to keep checkins on topic.

      Try to update other people's checkins instead of creating new files.

      Read other people's checkin notices before checking in your own to avoid simply duplicating what has already been said.

      Use a clear subject that describes what your checkin is about.

      Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive checkins might be purged. (You can maintain everything, even purged checkins, by adjusting your threshold on the User Preferences Page)

  2. slashdot business model by Anonymous Coward · · Score: 4, Funny

    1) Post advertisements as news articles
    2) ???????????????????
    3) Profit!!!!!!!!!!!!!!!!!

  3. Solution by jsse · · Score: 5, Funny

    ...and they just went out for lunch ... Argh! Did you know there is a solution to this problem?

    Go to lunch.

  4. Another one.. by droyad · · Score: 2, Funny

    The base ball bat. At my work after we beat the first few developers to a pulp after they checked in broken files, we found that the rate of broken files decreased dramatically