1. 04 1月, 2017 1 次提交
  2. 15 12月, 2016 1 次提交
  3. 18 11月, 2016 1 次提交
    • A
      [SECURITY-343] Restrict API access to NodeMonitor data · c19a56d2
      Andrew Bayer 提交于
      Switch to requiring EXTENDED_READ permission for access to NodeMonitor
      data. It might theoretically be better if we had more granular
      permissions on each NodeMonitor, but that's a bigger change, and since
      EXTENDED_READ is already what we use to limit access to serving the
      computer's config.xml, I think this is appropriate.
      c19a56d2
  4. 03 11月, 2016 1 次提交
  5. 02 11月, 2016 1 次提交
  6. 16 10月, 2016 1 次提交
  7. 03 10月, 2016 1 次提交
  8. 26 9月, 2016 1 次提交
  9. 21 7月, 2016 2 次提交
  10. 20 7月, 2016 1 次提交
    • P
      [JENKINS-34468] CLI command offline-node extracted from core to CLI (#2392) · fb7458f2
      Pavel Janousek 提交于
      * [JENKINS-34468] CLI command offline-node extracted from core to CLI
      
      offline-node extended to accept multiple node names
      offline-node covered by test-cases
      
      * Fixed translation properties
      
      * Fixes based on Oleg's comments
      
      * Fixed HelpCommandTest test-case
      
      * Minor fixes
      
      * Uses Matchers.instanceOf everywhere instead of Java operator instanceof
      fb7458f2
  11. 12 7月, 2016 1 次提交
  12. 08 7月, 2016 1 次提交
  13. 07 6月, 2016 1 次提交
  14. 22 5月, 2016 1 次提交
  15. 06 5月, 2016 1 次提交
  16. 05 5月, 2016 3 次提交
  17. 03 5月, 2016 1 次提交
  18. 09 3月, 2016 2 次提交
    • S
      Jenkins.getInstance() will be @Nonnull in Jenkins 2.0+ · 96150d3a
      Stephen Connolly 提交于
      - Code that is running from a plugin and on the master's JVM is guaranteed to never get null from this method (any cases where you do get null are bugs in core)
      - Code that is running from a plugin and on a remote JVM should never be allowed to load the Jenkins class in their classloader, so should never use Jenkins.getInstance()... we are annotating the method with @Nullable so that such code can have some evolution time
      - Code that is running in core and on one of two special paths should use the Jenkins.getInstanceOrNull() method so that the UI can be presented to users before the singleton has been instantiated / after the singleton has been destroyed
      - The remaining 95% of uses in core (and 100% of uses in plugins) can safely assume that the instance is never null
      96150d3a
    • S
      Revert "Jenkins.getInstance() should be non-null" · d1dfbd2b
      Stephen Connolly 提交于
      This reverts commit bb7c8fce.
      
      Closes #2090, I'll redo this as a PR... though if that PR is subject to multiple rounds of review before being merged then I will take that of evidence of the exact problem that committing directly was supposed to resolve... namely exponentially multiplying the effort required to make actual improvements to the code base.
      d1dfbd2b
  19. 08 3月, 2016 2 次提交
    • S
    • S
      Jenkins.getInstance() should be non-null · bb7c8fce
      Stephen Connolly 提交于
      - It is never too late to do the right thing.
      - The vast majority of usages of `Jenkins.getInstance()` in core currently assume that its return value is non-null
      - This commit changes those that are written to correctly check for non-null values will call `Jenkins.getInstanceOrNull()`
      - We deprecate the `Jenkins.getActiveInstance()` madness
      - I checked with @kohsuke who said not to bother with a PR and just commit this strongly opinionated change direct to master as a PR will just degrade into a bikeshedding.
      bb7c8fce
  20. 26 2月, 2016 1 次提交
  21. 03 2月, 2016 1 次提交
  22. 02 2月, 2016 1 次提交
  23. 30 1月, 2016 1 次提交
  24. 23 12月, 2015 1 次提交
  25. 02 12月, 2015 1 次提交
  26. 28 11月, 2015 1 次提交
  27. 19 11月, 2015 1 次提交
  28. 17 11月, 2015 1 次提交
  29. 04 11月, 2015 1 次提交
  30. 20 10月, 2015 1 次提交
  31. 10 9月, 2015 2 次提交
  32. 21 8月, 2015 1 次提交
  33. 20 8月, 2015 1 次提交
  34. 11 8月, 2015 1 次提交