1. 11 4月, 2017 1 次提交
  2. 12 2月, 2017 1 次提交
    • J
      Spelling fixes in changelogs, Javadoc, logs and UI (#2718) · 496703d0
      Josh Soref 提交于
      * spelling: abstract
      
      * spelling: about
      
      * spelling: absolute
      
      * spelling: across
      
      * spelling: activity
      
      * spelling: actually
      
      * spelling: addition
      
      * spelling: allocating
      
      * spelling: ambiguous
      
      * spelling: analyzes
      
      * spelling: analysis
      
      * spelling: another
      
      * spelling: appear
      
      * spelling: arbitrary
      
      * spelling: artifact
      
      * spelling: assignment
      
      * spelling: associated
      
      * spelling: augment
      
      * spelling: authentication
      
      * spelling: automatically
      
      * spelling: available
      
      * spelling: availability
      
      * spelling: because
      
      * spelling: background
      
      * spelling: beginning
      
      * spelling: boolean
      
      * spelling: browsers
      
      * spelling: building
      
      * spelling: calculation
      
      * spelling: channel
      
      * spelling: column
      
      * spelling: concatenation
      
      * spelling: connect
      
      * spelling: contribute
      
      * spelling: convert
      
      * spelling: copied
      
      * spelling: couldn't
      
      * spelling: scrambled
      
      * spelling: creates-a
      
      * spelling: curr-entry
      
      * spelling: customize
      
      * spelling: diagnostic
      
      * spelling: contain
      
      * spelling: default
      
      * spelling: delimiter
      
      * spelling: descriptor
      
      * spelling: disambiguates
      
      * spelling: different
      
      * spelling: diligently
      
      * spelling: disabled
      
      * spelling: discovered
      
      * spelling: display
      
      * spelling: doesn't
      
      * spelling: dollar
      
      * spelling: downstream
      
      * spelling: dynamically
      
      * spelling: preemptively
      
      * spelling: encrypt
      
      * spelling: erroneous
      
      * spelling: examine
      
      * spelling: existence
      
      * spelling: value
      
      * spelling: february
      
      * spelling: handling
      
      * spelling: hostname
      
      * spelling: convenient
      
      * spelling: identify
      
      * spelling: implementation
      
      * spelling: incorrect
      
      * spelling: individual
      
      * spelling: initialization
      
      * spelling: initialized
      
      * spelling: inputstream
      
      * spelling: instantiated
      
      * spelling: instantiation
      
      * spelling: intended
      
      * spelling: interpreted
      
      * spelling: interrupted
      
      * spelling: invocations
      
      * spelling: kern
      
      * spelling: localization
      
      * spelling: logger
      
      * spelling: malfunctioning
      
      * spelling: methods
      
      * spelling: monitor
      
      * spelling: mutator
      
      * spelling: multiple
      
      * spelling: object
      
      * spelling: configured
      
      * spelling: optionally
      
      * spelling: option
      
      * spelling: overridden
      
      * spelling: parameterized
      
      * spelling: parent
      
      * spelling: permissions
      
      * spelling: plugin
      
      * spelling: potentially
      
      * spelling: preferable
      
      * spelling: problems like
      
      * spelling: programmatically
      
      * spelling: property
      
      * spelling: reallocate
      
      * spelling: recommended
      
      * spelling: redirected
      
      * spelling: registered
      
      * spelling: reliable
      
      * spelling: remember
      
      * spelling: recurrence
      
      * spelling: repeatable
      
      * spelling: repeated
      
      * spelling: resource
      
      * spelling: retrieve
      
      * spelling: returned
      
      * spelling: revision
      
      * spelling: sandwich
      
      * spelling: separator
      
      * spelling: serialization
      
      * spelling: settings
      
      * spelling: shadow
      
      * spelling: should
      
      * spelling: someone
      
      * spelling: source
      
      * spelling: specified
      
      * spelling: style
      
      * spelling: subversion
      
      * spelling: sufficient
      
      * spelling: supplementary
      
      * spelling: suppressing
      
      * spelling: synchronization
      
      * spelling: synchronized
      
      * spelling: this
      
      * spelling: transitioning
      
      * spelling: termination
      
      * spelling: trying
      
      * spelling: truncatable
      
      * spelling: unknown
      
      * spelling: undeployed
      
      * spelling: unnecessary
      
      * spelling: unparseable
      
      * spelling: update
      
      * spelling: upper
      
      * spelling: verify
      
      * spelling: visible
      
      * spelling: warning
      
      * spelling: we're
      
      * spelling: whitespace
      
      * spelling: wide
      
      * spelling: with
      
      * spelling: workspace
      
      * spelling: yielding
      
      * spelling: to
      
      * spelling: by
      
      * spelling: the
      
      * spelling: hours
      496703d0
  3. 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
  4. 08 3月, 2016 2 次提交
    • S
      Jenkins.getInstance() is safe to assume non-null · 84bc8eca
      Stephen Connolly 提交于
      - Only ever called after extensions are on the classpath and before termination
      - Noting that the one valid check for null should actually be using a guard on extensions being available and not a check for null
      84bc8eca
    • 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
  5. 30 8月, 2014 1 次提交
  6. 09 6月, 2014 1 次提交
  7. 31 5月, 2014 3 次提交
  8. 26 5月, 2012 1 次提交
  9. 29 5月, 2011 2 次提交
  10. 07 2月, 2009 1 次提交
  11. 05 1月, 2007 5 次提交