[JENKINS-53608] Fix up incorrect method signatures on readResolve

[jenkins-infra-bot]

readResolve() should be ANY_ACCESS_MODIFIER Object readResolve() however there are a few uses in class where this is not the case.

These should be tidied up and fixed.

hudson/triggers/SCMTrigger.java:private void readResolve() {
jenkins/security/apitoken/ApiTokenStats.java:    private ApiTokenStats readResolve() {
jenkins/security/apitoken/ApiTokenStats.java:private SingleTokenStats readResolve() {

---

Originally reported by teilo, imported from: Fix up incorrect method signatures on readResolve

• status: Resolved
• priority: Minor
• component(s): core
• resolution: Fixed
• resolved: 2018-09-19T13:33:01+00:00
• votes: 0
• watchers: 2
• imported: 2025-11-24

Raw content of original issue

readResolve() should be ANY_ACCESS_MODIFIER Object readResolve()  however there are a few uses in class where this is not the case.

These should be tidied up and fixed.


hudson/triggers/SCMTrigger.java:        private void readResolve() {
jenkins/security/apitoken/ApiTokenStats.java:    private ApiTokenStats readResolve() {
jenkins/security/apitoken/ApiTokenStats.java:        private SingleTokenStats readResolve() {

[jenkins-infra-bot]

• Remote link associated with this issue:

  • PR 3631

[jenkins-infra-bot]

olivergondza:

• Original comment link
• Raw content of original comment:

  I am hesitant to backport this as it does not address any customer issue while being potentially risky.
  

I am hesitant to backport this as it does not address any customer issue while being potentially risky.

[jenkins-infra-bot]

teilo:

• Original comment link
• Raw content of original comment:

  danielbeck requested the backport. I as the reporter personally have no need of one. The only thing I can think may be impacted is if a user has set 1000000 as the SCM threads and that the `readResolve` does not kick in there to limit it to {{MAX_SCM_THREAD}}s.  But that can be fixed without a code change if the user hits the issue (that may not even be an issue)
  

danielbeck requested the backport. I as the reporter personally have no need of one. The only thing I can think may be impacted is if a user has set 1000000 as the SCM threads and that the `readResolve` does not kick in there to limit it to {{MAX_SCM_THREAD}}s.  But that can be fixed without a code change if the user hits the issue (that may not even be an issue)

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  Agreed.
  

Agreed.