Simplify failing builder lists.

Tools/GardeningServer/model/ct-commit-log.html

 <!--
 Copyright 2014 The Chromium Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 -->
 
 <link rel='import' href='ct-commit.html'>
 
 <script>
 function CTCommitLog() {
@@ skipping 12 matching lines @@
 CTCommitLog.prototype.update = function() {
   // FIXME: Turn net.js into net.html and import it at the top of this file.
   return net.xml('http://blink.lc/blink/atom').then(this._processXml.bind(this));
 }
 
 CTCommitLog.prototype._processXml = function(xml) {
   Array.prototype.forEach.call(xml.getElementsByTagName('entry'), function(logentry) {
     var author = logentry.getElementsByTagName('author')[0].textContent.trim();
     var message = logentry.getElementsByTagName('content')[0].textContent.trim();
     // FIXME: Handle base urls for different repos.
-    // FIXME: This class should import config.js if it keeps using config.*.
-    var commit = new CTCommit(author, message, config.kBlinkRevisionURL);
+    var commit = new CTCommit(author, message, 'http://src.chromium.org/viewvc/blink');

[michaelpg, 2014/07/22 05:58:23]

why is it better for this to be hard-coded? what will change when we want to
show chromium commits?

[ojan, 2014/07/22 06:08:50]

We'll need to pass this information through in the constructor. So, hard-coding
it here for now made sense to me.

     this.commits[commit.revision] = commit;
   }.bind(this));
 }
-</script>
+</script>