+1 Great writing! ________________________________________ From: Leif Hedstrom [zw...@apache.org] Sent: Tuesday, February 10, 2015 8:09 PM To: dev Subject: On git master being stable, CI and everything
Hi all, this is a reminder to all our developers that our master tree is expected to be stable. A few tips 1. In most cases, if the CI fails, you ought to get an email from jenk...@ci.trafficserver.apache.org <mailto:jenk...@ci.trafficserver.apache.org>. This does not always works (e.g. for some jobs it can not find the commit at fault), in which case the emails are sent to iss...@trafficserver.apache.org <mailto:iss...@trafficserver.apache.org>. 2. You can always do a quick glance at the CI, to see if something is broken. This literally takes a few seconds: https://ci.trafficserver.apache.org <https://ci.trafficserver.apache.org/> Just look at the top, the “Unstable Jobs” should be empty. If it’s not, it’s broken, and you can dig into details by clicking the failed job. 3. If you break CI, you are expected to fix it as soon as possible. If you can’t it in a timely manner, the appropriate action is to back out the commit that failed. Having CI in a failed state impacts all developers. 4. If you make changes to the build system, I *strongly* recommend that you test both in-tree and out-of-tree builds *before* you commit. Completely failing builds make things like “git bisect” really troublesome. 5. Our primary runtime and development platform is Linux. Test your (non-trivial) commits on at least one Linux platform please. 6. Our oldest supported distribution is CentOS5. It’s not a bad idea to have a VM with this build environment (64-bit). Not a requirement though, but you are expected to fix builds that fail on CentOS5. (This will change with ATS 6.0, where we move to CentOS6 as the oldest version). 7. Many of us are working hard on cleaning up Coverity issues. Therefore, new Coverity issues should generally be considered “build breakage”, and the commit causing a new Coverity issue is responsible for fixing it. Therefore, keep an eye on the daily Coverity reports. Cheers, — leif
