1. 21 11月, 2018 1 次提交
  2. 02 8月, 2018 1 次提交
  3. 24 1月, 2018 3 次提交
  4. 15 12月, 2017 1 次提交
  5. 14 12月, 2017 1 次提交
  6. 14 10月, 2017 1 次提交
    • J
      [JENKINS-46759] Fixed bug in build queue filtering for views (#3008) · ce2d0f97
      Jon 提交于
      * [JENKINS-46759] Fixed bug related to views which filters build queue, jobs which has multiple sub steps were filtered incorrectly.
      
      * Added test case for build queue filtering in views.
      
      * [JENKINS-46759] Improved code based on feedback from PR; Fixed logic bug, moved logic to separate method and added limit to number of iteration when looking for owner task.
      ce2d0f97
  7. 03 9月, 2017 1 次提交
  8. 24 8月, 2017 1 次提交
  9. 13 8月, 2017 1 次提交
  10. 20 5月, 2017 1 次提交
    • J
      Adding some interface default method implementations (#2879) · d13b1361
      Jesse Glick 提交于
      * Adding some interface default method implementations rather than catching AbstractMethodError or providing partial implementation classes.
      
      * Show Javadoc warnings and errors, but not ‘Generating …/core/target/site/apidocs/jenkins/model/lazy/class-use/AbstractLazyLoadRunMap.html...’ and the like.
      
      * Javadoc fixes.
      
      * Review comments from @oleg-nenashev.
      
      * Test fixes.
      
      * Remove the unused import
      d13b1361
  11. 04 5月, 2017 1 次提交
  12. 03 5月, 2017 2 次提交
  13. 02 5月, 2017 2 次提交
  14. 11 4月, 2017 1 次提交
  15. 01 2月, 2017 2 次提交
  16. 31 1月, 2017 1 次提交
  17. 04 11月, 2016 1 次提交
  18. 27 10月, 2016 4 次提交
  19. 13 10月, 2016 2 次提交
  20. 10 10月, 2016 1 次提交
    • A
      Update XStream drive to improve performance in xml serilization/deserialization (#2561) · 8888296e
      Akbashev Alexander 提交于
      * Update XStream drive to improve performance in xml serilization/deserialization
      
      According XStream FAQ (http://x-stream.github.io/faq.html#Scalability):
      
      XStream is a generalizing library, it inspects and handles your types on
      the fly. Therefore it will normally be slower than a piece of optimized
      Java code generated out of a schema. However, it is possible to increase
      the performance anyway:
      
      * Write custom converters for those of your types that occur very often in
      your XML.
      * Keep a configured XStream instance for multiple usage. Creation and
      initialization is quite expensive compared to the overhead of XStream
      when calling marshall or unmarshal.
      * Use Xpp3 or StAX parsers.
      
      So, I decided to move from old Xpp to new Xpp3.
      
      * Change other occurance of XppDriver to Xpp3Driver as well
      8888296e
  21. 03 10月, 2016 1 次提交
  22. 17 4月, 2016 1 次提交
  23. 06 4月, 2016 1 次提交
  24. 05 4月, 2016 1 次提交
  25. 02 4月, 2016 1 次提交
  26. 30 3月, 2016 1 次提交
  27. 24 3月, 2016 1 次提交
  28. 23 3月, 2016 1 次提交
  29. 22 3月, 2016 3 次提交