1. 17 7月, 2013 2 次提交
  2. 16 7月, 2013 2 次提交
  3. 15 7月, 2013 1 次提交
  4. 12 7月, 2013 1 次提交
  5. 11 7月, 2013 1 次提交
  6. 10 7月, 2013 1 次提交
    • J
      [JENKINS-17728] Fixing another possible cause of an NPE. · 06c211c6
      Jesse Glick 提交于
      Unlike the bug I originally reproduced, in which the parent had some builds
      but the context in which the new build was scheduled omits a parent,
      this seems to be due to a case in which there is no build record at all for the parent.
      No idea how that could happen (getLastBuild should return even a running, failed, or aborted build),
      but @treydock reports a stack trace in 1.509.2 which implies this.
      So fixing null safety; will not prevent an exception but will report it more gracefully.
      06c211c6
  7. 07 7月, 2013 1 次提交
  8. 06 7月, 2013 2 次提交
  9. 05 7月, 2013 1 次提交
    • K
      [FIXED JENKINS-18585] · 059e6081
      Kohsuke Kawaguchi 提交于
      The earlier fix by @ssogabe broke the test. This fix corrects the
      problem properly.
      
      The reason this error happens with some plugins is that if there's an
      input field whose name is "on", then even after prototype.js extends
      an element object, "form.on" will refer to the input element, not the
      prototype.js function to add an event handler.
      059e6081
  10. 03 7月, 2013 3 次提交
  11. 02 7月, 2013 2 次提交
  12. 29 6月, 2013 1 次提交
  13. 27 6月, 2013 1 次提交
  14. 26 6月, 2013 5 次提交
  15. 25 6月, 2013 1 次提交
    • K
      [FIXED JENKINS-15437] · d3575548
      Kohsuke Kawaguchi 提交于
      The exception handler ended up adding almost all the headers again,
      resulting in a lot of duplicate headers.
      
      Most critically, stapler was adding "Content-Encoding" header twice,
      breaking browsers.
      d3575548
  16. 22 6月, 2013 1 次提交
  17. 21 6月, 2013 3 次提交
  18. 20 6月, 2013 4 次提交
  19. 19 6月, 2013 5 次提交
  20. 18 6月, 2013 2 次提交