- 25 6月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
-
- 23 6月, 2014 3 次提交
-
-
由 Oliver Gondža 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 19 6月, 2014 1 次提交
-
-
由 tfennelly 提交于
-
- 18 6月, 2014 1 次提交
-
-
由 Oliver Gondža 提交于
-
- 17 6月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-14264] For logs >200Kb, just show two <t:task>s without nesting, for proper interoperability with the context menu.
-
由 Jesse Glick 提交于
[FIXED JENKINS-23191] f:radio is not databinding-aware and does not correctly handle multiple configuration sections unless you make it.
-
- 16 6月, 2014 4 次提交
-
-
由 Oliver Gondža 提交于
-
由 Oliver Gondža 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 14 6月, 2014 1 次提交
-
-
由 tfennelly 提交于
-
- 13 6月, 2014 1 次提交
-
-
由 Jesse Glick 提交于
-
- 12 6月, 2014 4 次提交
-
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
Integrated the fix made in winp 1.20.
-
由 Daniel Beck 提交于
-
由 Oleg Nenashev 提交于
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
-
- 11 6月, 2014 2 次提交
-
-
由 Daniel Beck 提交于
-
由 Daniel Beck 提交于
-
- 10 6月, 2014 6 次提交
-
-
由 Jesse Glick 提交于
[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.
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
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.
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 09 6月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
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.
-
- 03 6月, 2014 3 次提交
-
-
由 Oleg Nenashev 提交于
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
- 02 6月, 2014 6 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Oleg Nenashev 提交于
-
由 Oleg Nenashev 提交于
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
-
由 Oliver Gondža 提交于
-
由 Oliver Gondža 提交于
-
由 Oliver Gondža 提交于
-
- 01 6月, 2014 3 次提交
-
-
由 Oliver Gondža 提交于
-
由 Oleg Nenashev 提交于
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
-
由 Daniel Beck 提交于
-