1. 15 10月, 2015 1 次提交
  2. 30 9月, 2015 1 次提交
  3. 29 9月, 2015 3 次提交
  4. 25 9月, 2015 1 次提交
  5. 16 9月, 2015 4 次提交
  6. 10 9月, 2015 6 次提交
  7. 03 9月, 2015 2 次提交
  8. 20 8月, 2015 3 次提交
    • J
      [JENKINS-29936] when removing an item use ACL.SYTEM. · 9a63d6f8
      James Nord 提交于
      The OldDataMonitor should be using ACL.system not the ACL of the calling
      thread - this also avoids the deadlock when an authorization strategy is
      being saved (locking the auth strategy) which will call into the ODM at
      the same point the ODM is being called an a Run has been saved (which will
      cause a lookup of the job which will do a permissions check).
      
      (cherry picked from commit 8a077a80)
      9a63d6f8
    • S
      [FIXED JENKINS-29568] A better fix · db1e2d2a
      Stephen Connolly 提交于
      - 252e1296 doesn't work for all cases as there are code paths
        where a pending launch can be removed from the pending list and not have spent() called.
      - There was no reason for iterating the list twice anyway, as all of this takes place with the locks held
      - My notifying each one as we process, if there is an Error, we will not leave any stranded. The next run
        through, if there is one, will cover those instances.
      
      (cherry picked from commit 4f0ca16b)
      db1e2d2a
    • S
      The call to PlannedNode.spent() *must* always occur · f2500bd5
      Stephen Connolly 提交于
      - They have been removed from the pendingLaunches, so once we leave this method we have no reference to them
      - Arguably the call to spent should take place when removing from the pendingLaunches, but that would change
        the method contract
      
      (cherry picked from commit 252e1296)
      f2500bd5
  9. 18 8月, 2015 1 次提交
  10. 16 8月, 2015 2 次提交
  11. 14 8月, 2015 1 次提交
    • J
      [JENKINS-29936] when removing an item use ACL.SYTEM. · 8a077a80
      James Nord 提交于
      The OldDataMonitor should be using ACL.system not the ACL of the calling
      thread - this also avoids the deadlock when an authorization strategy is
      being saved (locking the auth strategy) which will call into the ODM at
      the same point the ODM is being called an a Run has been saved (which will
      cause a lookup of the job which will do a permissions check).
      8a077a80
  12. 13 8月, 2015 2 次提交
  13. 11 8月, 2015 6 次提交
  14. 10 8月, 2015 4 次提交
  15. 07 8月, 2015 3 次提交