- 12 6月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
Move entries older than last year to changelog-old
-
- 11 6月, 2014 8 次提交
-
-
由 Harald Albers 提交于
Fix translation error
-
由 Jesse Glick 提交于
[JENKINS-23365] Follow-up API fixes: introduce SCM.getKey(), and add an SCMRevisionState baseline argument to checkout. Necessary in order to produce correct changelogs by SCM plugins which actually use SCMRevisionState correctly (unlike git-plugin!). (cherry picked from commit df9dc4c8)
-
由 Jesse Glick 提交于
(cherry picked from commit abf33593)
-
由 Bruno Kühnen Meneguello 提交于
-
由 Daniel Beck 提交于
-
由 CloudBees DEV@Cloud 提交于
-
由 Daniel Beck 提交于
-
由 Jesse Glick 提交于
-
- 10 6月, 2014 18 次提交
-
-
由 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.
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
[JENKINS-19310] Unreproducible failure of DirectlyModifiableViewTest.failWebMethodForIllegalRequest, probably from a StackOverflowError. at … at hudson.model.View.toString(View.java:514) at java.text.MessageFormat.subformat(MessageFormat.java:1246) at java.text.MessageFormat.format(MessageFormat.java:836) at java.text.Format.format(Format.java:140) at java.text.MessageFormat.format(MessageFormat.java:812) at java.util.logging.Formatter.formatMessage(Formatter.java:130) at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:63) at java.util.logging.StreamHandler.publish(StreamHandler.java:179) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88) at java.util.logging.Logger.log(Logger.java:481) at java.util.logging.Logger.doLog(Logger.java:503) at java.util.logging.Logger.log(Logger.java:567) at hudson.model.AbstractItem.getUrl(AbstractItem.java:423) at hudson.model.View.getViewUrl(View.java:510) at hudson.model.View.toString(View.java:514) at …
-
由 CloudBees DEV@Cloud 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 CloudBees DEV@Cloud 提交于
-
由 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 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
Corrects 9ce6b0fe.
-
由 Jesse Glick 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 09 6月, 2014 8 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
Existing code referring to a member of type AbstractBuild often called methods not present in Run. Changed to retain the existing fields and getters but deprecating them and introducing replacements.
-
由 Jesse Glick 提交于
Fix of JENKINS-8408 broke some tests of workspace-based polling; disable the fix when inside a test, for better predictability. (Ideally Jenkins would actually detect whether there was a *plan* to connect a slave of a given name.)
-
由 Jesse Glick 提交于
-
由 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.
-
- 07 6月, 2014 5 次提交
-
-
由 Kohsuke Kawaguchi 提交于
I came into this use case while working on the workflow, but I think it's useful in other context as well, such as Scriptler plugin needing to define some parameters.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-