- 16 5月, 2013 3 次提交
-
-
由 Donny Nadolny 提交于
-
-
由 Donny Nadolny 提交于
-
- 15 5月, 2013 1 次提交
-
-
由 Jesse Glick 提交于
-
- 14 5月, 2013 2 次提交
-
-
由 Jesse Glick 提交于
Amends lvotypko’s 33e0df78 to be as careful as bdff4254 + f65da7f9 + 10e9b002 for persistent actions.
-
由 Jesse Glick 提交于
-
- 13 5月, 2013 3 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
- 11 5月, 2013 1 次提交
-
-
由 Jesse Glick 提交于
-
- 10 5月, 2013 1 次提交
-
-
由 imod 提交于
-
- 09 5月, 2013 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 08 5月, 2013 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 ssogabe 提交于
-
- 07 5月, 2013 12 次提交
-
-
由 olivergondza 提交于
Use build parameters in combination filters
-
由 Oliver Gondža 提交于
Based on the work of Michael Elkin [1]. [1] https://issues.jenkins-ci.org/secure/attachment/20588/0001-tag-1.414-for-parameters-in-multiconfig-filters.patch
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
Invalid request submission: {json=[Ljava.lang.String;@2c46358e, .crumb=[Ljava.lang.String;@35661457} Diagnostics added in 21bf5c45. Failing I think because message.groovy uses f.submit rather than a plain <input type="submit">, so JSON gets created and then StaplerRequest.getParameter cannot find it. But if this is the problem then why would it ever work? Perhaps a timing issue: JavaScript is used to massage the form just prior to submission, and maybe this only happens sometimes? Cannot reproduce test failure locally.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 06 5月, 2013 4 次提交
-
-
由 Olivier Lamy 提交于
changelog entry for JENKINS-17858
-
由 Olivier Lamy 提交于
[FIXED JENKINS-17858] allow <f:dropdownDescriptorSelector> to be defaulting to an instance
-
由 Olivier Lamy 提交于
changelog entry for JENKINS-17723
-
由 Olivier Lamy 提交于
FIXES JENKINS-17723 - Default maven settings Good change !
-
- 05 5月, 2013 2 次提交
- 04 5月, 2013 1 次提交
-
-
由 imod 提交于
-
- 03 5月, 2013 3 次提交
-
-
由 dnadolny 提交于
[FIXED JENKINS-17478] Add extension point to rewrite JUnit test names
-
由 Jesse Glick 提交于
If an optional component cannot be loaded, print a polite one-line message, not a big scary stack trace. (To reproduce: BuildNowTextPropertyTest from cloudbees-template warns about FolderProxyGroupContainer.)
-
由 Donny Nadolny 提交于
This adds an extension point, TestNameTransformer, which is called to transform JUnit test case names. This is useful for JVM languages like scala which are more flexible than java with identifier naming. Scala, for example, allows you to write test names between back ticks, and then encodes the name using valid java identifiers. This extension point would allow a plugin to transform those names back in to readable names when they are displayed on the test result page.
-
- 02 5月, 2013 2 次提交
-
-
由 Jesse Glick 提交于
https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/850/testReport/jenkins.security/RekeySecretAdminMonitorTest/testBasicWorkflow/ com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 400 Bad Request for http://localhost:60027//administrativeMonitor/jenkins.security.RekeySecretAdminMonitor/scan at com.gargoylesoftware.htmlunit.WebClient.throwFailingHttpStatusCodeExceptionIfNecessary(WebClient.java:549) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:333) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:357) at com.gargoylesoftware.htmlunit.html.HtmlForm.submit(HtmlForm.java:196) at org.jvnet.hudson.test.HudsonTestCase.submit(HudsonTestCase.java:1178) at jenkins.security.RekeySecretAdminMonitorTest.testBasicWorkflow(RekeySecretAdminMonitorTest.java:112) java.lang.Exception: Invalid request submission at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:79) at jenkins.security.RekeySecretAdminMonitor.doScan(RekeySecretAdminMonitor.java:117)
-
由 Jesse Glick 提交于
-