Hi all,

We just had 2 commits cause failures on builds.apache.org, and I reverted them 
right now.

https://builds.apache.org/job/Ambari-trunk-Commit/1865/ due to a rat check 
failure because of 
AMBARI-9795<https://issues.apache.org/jira/browse/AMBARI-9795>
and
https://builds.apache.org/job/Ambari-trunk-Commit/1868/ due to unit test 
failure because of 
AMBARI-9777<https://issues.apache.org/jira/browse/AMBARI-9777>

We need to be extra careful since we we are hardening a release candidate as 
well.
I understand that builds can often take a couple of hours to finish, so please 
follow these steps

  *   Run local unit tests first, especially since rat-check failures are easy 
to detect
  *   Commit first to trunk, then check the builds.apache.org unit test results 
before committing to branch-2.0.0
  *   Be vigilant; if a commit breaks either trunk or branch-2.0.0, then revert 
it and inform the committer
  *   If committing on a Friday, pay extra attention to avoid a broken build 
throughout the weekend

http://memegenerator.net/instance/59605746

Thanks,
Alejandro

Reply via email to