Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In practice this map is always empty, since I checked Jenkins and CloudBees sources and nothing ever writes to the map. The only reader besides Stapler is https://github.com/jenkinsci/scm-api-plugin/blob/a24e62fa67977d1c381b922a1a745afb725771c7/src/main/java/jenkins/scm/api/SCMFile.java#L422. Altogether I can't see a good reason to retain this feature; the servlet container should always be the source of truth and this seems like yet another case of Stapler over-reaching in scope. Simpler to deprecate this feature and remove it eventually.
Testing done
mvn clean verify
Submitter checklist