Update job status based just on the final job result

Update job status based just on the final job result This is especially useful for try jobs where some step failures are not fatal (e.g. recipe-based builders that deapply the patch and retry failing tests).

[phajdan.jr, 2014-01-14 21:54:54]

Please see http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel/bu... for an example. The tryserver box on Rietveld shows up as red, but should be green because the job is successful.

[iannucci, 2014-01-17 00:48:53]

+M-A for FYI This looks good to me, just 1 question. https://codereview.appspot.com/49430044/diff/1/templates/patchset.html File templates/patchset.html (right): https://codereview.appspot.com/49430044/diff/1/templates/patchset.html#newcod... templates/patchset.html:115: {%if try_job.url %} what's this change for?

[phajdan.jr, 2014-01-17 01:03:09]

https://codereview.appspot.com/49430044/diff/1/templates/patchset.html File templates/patchset.html (right): https://codereview.appspot.com/49430044/diff/1/templates/patchset.html#newcod... templates/patchset.html:115: {%if try_job.url %} On 2014/01/17 00:48:53, iannucci wrote: > what's this change for? First build has a buildnumber=0 (that came up during my testing). Given what is inside this "if" block (href) it should be really testing for url instead of buildnumber.

[iannucci, 2014-01-17 01:04:00]

Makes sense to me. LGTM.

[iannucci, 2014-01-25 15:44:48]

On 2014/01/17 01:04:00, iannucci wrote: > Makes sense to me. LGTM. Committed as https://code.google.com/p/rietveld/source/detail?r=4da88725d511fb4d19260aab7e...