1. 28 10月, 2014 1 次提交
    • M
      Change Jenkins to use a single consistent data-binding field. · 81ebb628
      Matt Moore 提交于
      See also: https://github.com/stapler/stapler/pull/39
      
      This commit includes several changes to accomodate the above change in Stapler (moving away from 'stapler-class'), as well as to make Jenkins consistently use this same JSON field (moving away from 'kind').
      
      NOTE: Stapler will continue to accept 'stapler-class' for backwards compatibility, and similarly this plugin will continue to pass 'stapler-class' for plugins that have keyed off of it.
      81ebb628
  2. 27 10月, 2014 13 次提交
  3. 26 10月, 2014 4 次提交
  4. 25 10月, 2014 1 次提交
  5. 24 10月, 2014 2 次提交
  6. 21 10月, 2014 1 次提交
    • J
      Null safety. · 90292ed2
      Jesse Glick 提交于
      Observed in a test against 1.480:
      … hudson.model.Executor run
      SEVERE: Unexpected executor death
      java.lang.NullPointerException
      	at hudson.model.Computer.getNode(Computer.java:473)
      	at hudson.slaves.SlaveComputer.getNode(SlaveComputer.java:177)
      	at hudson.slaves.SlaveComputer.getRetentionStrategy(SlaveComputer.java:609)
      	at hudson.slaves.SlaveComputer.taskCompleted(SlaveComputer.java:285)
      	at hudson.model.queue.WorkUnitContext.synchronizeEnd(WorkUnitContext.java:140)
      	at hudson.model.Executor.run(Executor.java:253)
      90292ed2
  7. 20 10月, 2014 10 次提交
  8. 19 10月, 2014 1 次提交
  9. 18 10月, 2014 1 次提交
  10. 17 10月, 2014 5 次提交
  11. 16 10月, 2014 1 次提交