Using Memcached to Explore NoSQL
Neo4j App Performance Profile Management using New Relic
Embedded Jetty, Vaadin and Weld
PyPy 1.8 Improves Performance, Maintains Business As Usual
JSR 356: Java API for WebSocket
I’m a 17 year old developer up against a 19 year old, his company and a $1.1M investment
What I learned interviewing with Google  | |
| HTML5 Canvas | |
| Written by: Simon Sarris | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
By bloid
via alittlemadness.com
Published: Nov 22 2008 / 00:42
Comments
John_Idol replied ago:
it can break but you need to fix it as soon as you find out
Dave Newton replied ago:
Huh? If the build breaks locally why would you check it in to the CI server? Then everybody else's build breaks too when they check out new stuff (unless you have a two-stage commit process--which means the golden build never breaks). I'm confused.
jsankey replied ago:
My post does not suggest you would deliberately break the build in this way! When I mention local smoke testing I mean you run a build and test locally, making sure it passes before you commit. You certainly never commit /knowing/ you will break the build. I'm just saying that you shouldn't be hung up on trying to guarantee unbreakability, because it is usually impractical and has its own costs. I'll have to work on my clarity :).
Voters For This Link (9)
Voters Against This Link (4)