1. 07 5月, 2013 1 次提交
    • J
      Frequent test failure on PR builder. · f6662a8f
      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.
      f6662a8f
  2. 06 5月, 2013 4 次提交
  3. 05 5月, 2013 2 次提交
  4. 04 5月, 2013 1 次提交
  5. 03 5月, 2013 3 次提交
    • D
      Merge pull request #769 from dnadolny/master · 4e370843
      dnadolny 提交于
      [FIXED JENKINS-17478] Add extension point to rewrite JUnit test names
      4e370843
    • J
      If an optional component cannot be loaded, print a polite one-line message,... · 53d1e20f
      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.)
      53d1e20f
    • D
      Add extension point to rewrite JUnit test names · d658f55c
      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.
      d658f55c
  6. 02 5月, 2013 18 次提交
  7. 01 5月, 2013 6 次提交
  8. 30 4月, 2013 3 次提交
  9. 29 4月, 2013 2 次提交