Skip to content
  1. Jun 18, 2014
  2. Jun 17, 2014
  3. Jun 16, 2014
  4. Jun 13, 2014
  5. Jun 12, 2014
  6. Jun 11, 2014
  7. Jun 10, 2014
    • Daniel Beck's avatar
      JENKINS-22028 was only fixed in 1.565 · 9f3e1d81
      Daniel Beck authored
      9f3e1d81
    • Jesse Glick's avatar
      [FIXED JENKINS-20327] When saving a list view, submit POST data with size... · adfa9a30
      Jesse Glick authored
      [FIXED JENKINS-20327] When saving a list view, submit POST data with size proportional to the # of jobs selected for inclusion, not the number of options.
      This can be done easily by setting json="true"; otherwise the default is to pass =false for each unselected job.
      Ironically, even with this fix we are sending 2× what is needed,
      since currently ListView.submit does not even check the json parameter for job names:
      it only pays attention to top-level request parameters that the browser defines for selected checkboxes.
      Ideally we could ask buildFormTree to ignore a given form element entirely, so as to avoid the wasted data.
      2 tags
      adfa9a30
    • Kohsuke Kawaguchi's avatar
      creating an RC branch · 3651b0f0
      Kohsuke Kawaguchi authored
      3651b0f0
    • Jesse Glick's avatar
      [FIXED JENKINS-19310] Provide correct links for build history inside a folder. · ea954349
      Jesse Glick authored
      The basic fix is to use ${rootURL} plus full model object URLs rather than relying on ${jobBaseUrl}.
      This is made trickier by the fact that the model object URLs are computed inside ProgressiveRendering.compute,
      and therefore will not be correct when nondefault views are in the crumb trail unless the original request information is present.
      So modifying ProgressiveRendering to preserve a copy of the original request for use during computation.
      (This could probably be used to simplify parts of AsynchPeople as well.)
      Also improving AbstractItem.getUrl to properly construct a URL including views even when the current page is not inside the item;
      it should suffice for some ancestor of the current item (or a view thereof) to be in the ancestor list of this page.
      changes/160
      ea954349
    • Kohsuke Kawaguchi's avatar
      ad2e7d6d
  8. Jun 09, 2014
  9. Jun 08, 2014
    • Kohsuke Kawaguchi's avatar
      [FIXED JENKINS-23228] · c95777e4
      Kohsuke Kawaguchi authored
      Documented this feature and integrated a newer version of Stapler.
      
      I took the opportunity to reorder the content in the section, so that
      the tree parameter becomes the main subject.
      
      At this point, the depth parameter should be only used in a limited
      circumstance, so it should be treated as such.
      c95777e4
  10. Jun 03, 2014
  11. Jun 02, 2014
  12. Jun 01, 2014