- 04 1月, 2017 1 次提交
-
-
由 Andrew Bayer 提交于
-
- 15 12月, 2016 1 次提交
-
-
由 Stephen Connolly 提交于
- Also switch in cases where we have a subset that is likely significantly smaller and hence quicker to sort
-
- 18 11月, 2016 1 次提交
-
-
由 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.
-
- 03 11月, 2016 1 次提交
-
- 02 11月, 2016 1 次提交
-
-
由 Stephen Connolly 提交于
-
- 16 10月, 2016 1 次提交
-
-
由 Oliver Gondža 提交于
* Avoid deprecated findbugs annotations * One more forgotten annotation
-
- 03 10月, 2016 1 次提交
-
-
由 Nicolas De Loof 提交于
-
- 26 9月, 2016 1 次提交
-
-
由 Ted 提交于
-
- 21 7月, 2016 2 次提交
-
-
由 Ing. Pavel Janousek 提交于
wait-node-online and wait-node-offline covered by test-cases
-
由 Sebastien Guillemot 提交于
* no longer hard-code the icon for the executor panel [FIXED JENKINS-36775] * add documentation to Computer.java for custom icons * add recommended implementation to the javadoc
-
- 20 7月, 2016 1 次提交
-
-
由 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
-
- 12 7月, 2016 1 次提交
-
-
由 Pavel Janousek 提交于
* [JENKINS-35570] List of computer's names extracted to Util
-
- 08 7月, 2016 1 次提交
-
-
由 Jesse Glick 提交于
-
- 07 6月, 2016 1 次提交
-
-
由 Nicolas De Loof 提交于
Signed-off-by: NNicolas De Loof <nicolas.deloof@gmail.com>
-
- 22 5月, 2016 1 次提交
-
-
由 Pavel Janousek 提交于
* [JENKINS-31417] CLI command connect-node extracted from core to CLI connect-node extended to accept multiple node names connect-node covered by test-cases * Slighty modified Javadoc * Fixed translations after rebase
-
- 06 5月, 2016 1 次提交
-
-
由 Oliver Gondža 提交于
-
- 05 5月, 2016 3 次提交
-
-
由 Pavel Janousek 提交于
-
由 Ing. Pavel Janousek 提交于
-
由 Ing. Pavel Janousek 提交于
disconnect-node extended to accept multiple node names disconnect-node covered by test-cases
-
- 03 5月, 2016 1 次提交
-
-
由 Ing. Pavel Janousek 提交于
Functionality was moved to OnlineNodeCommand class already
-
- 09 3月, 2016 2 次提交
-
-
由 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
-
由 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.
-
- 08 3月, 2016 2 次提交
-
-
由 Stephen Connolly 提交于
-
由 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.
-
- 26 2月, 2016 1 次提交
-
-
由 Jesse Glick 提交于
Computer.CREATE should be scoped to JENKINS, not COMPUTER, since it is checked on Jenkins, not a Node or Computer. Compare Item.CREATE, scoped to ITEM_GROUP, not ITEM.
-
- 03 2月, 2016 1 次提交
-
-
由 Christopher Simons 提交于
This change adds code to check that the user isn't attempting to rename an existing node with the name of another existing node. Previous to this change, such rename operations would succeed and would corrupt node configuration data. (cherry picked from commit 16d6429c)
-
- 02 2月, 2016 1 次提交
-
-
由 Antonio Muñiz 提交于
-
- 30 1月, 2016 1 次提交
-
-
由 Antonio Muñiz 提交于
-
- 23 12月, 2015 1 次提交
-
-
由 Christopher Simons 提交于
This change adds code to check that the user isn't attempting to rename an existing node with the name of another existing node. Previous to this change, such rename operations would succeed and would corrupt node configuration data.
-
- 02 12月, 2015 1 次提交
-
-
由 Ing. Pavel Janousek 提交于
online-node covered by test-cases
-
- 28 11月, 2015 1 次提交
-
-
由 Ted 提交于
-
- 19 11月, 2015 1 次提交
-
-
由 Johannes Ernst 提交于
* moved to jenkins.util.SystemProperties * consistent naming getString/getInteger/getBoolean * improved code formatting Improved JavaDoc
-
- 17 11月, 2015 1 次提交
-
-
由 Johannes Ernst 提交于
Accomplished by centralizing calls to System.getProperty(String) and related into new file SystemProperties.java. There, we first check for existence of system property; if not, we look for property in context.xml This is done for "application" properties (like hudson.DNSMultiCast.disabled) but not for java properties (like user.name)
-
- 04 11月, 2015 1 次提交
-
-
由 Christopher Simons 提交于
-
- 20 10月, 2015 1 次提交
-
-
由 Stephen Connolly 提交于
- Also tidy up some of the mess logic in both #1866 and #1860
-
- 10 9月, 2015 2 次提交
-
-
由 James Nord 提交于
(cherry picked from commit d72d7b83)
-
由 James Nord 提交于
Node objects are owned by the Nodes class not by Jenkins so NodeProperties and anything modifiying them needs to be updated. Also modifying Nodes requires a lock on the Queue so use this lock not Jenkins to prevent the deadlock observed in JENKINS-30057 (cherry picked from commit 06f690db)
-
- 21 8月, 2015 1 次提交
-
-
由 James Nord 提交于
-
- 20 8月, 2015 1 次提交
-
-
由 James Nord 提交于
Node objects are owned by the Nodes class not by Jenkins so NodeProperties and anything modifiying them needs to be updated. Also modifying Nodes requires a lock on the Queue so use this lock not Jenkins to prevent the deadlock observed in JENKINS-30057
-
- 11 8月, 2015 1 次提交
-
-