Add new LargeText interface based constructor for AnnotatedLargeText

[das7pad]

• Part of Viewing large logs runs out of memory pipeline-graph-view-plugin#704
• Exports Add interface based constructor for LargeText stapler#718
• For Implement non-buffered streaming for step logs workflow-api-plugin#438

This PR is adding an interface based constructor for AnnotatedLargeText. The workflow-api plugin will make use of it for implementing a streaming based step log (jenkinsci/workflow-api-plugin#438).

Testing done

The interface based constructor is tested in stapler and jenkinsci/workflow-api-plugin#438.

Proposed changelog entries

• Add interface based constructor for AnnotatedLargeText.

Proposed changelog category

/remove-label work-in-progress

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

Before the changes are marked as ready-for-merge:

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[das7pad]

/label developer

[timja]

(do not merge isn't needed if its a draft PR..)

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[das7pad]

@timja have you considered adding a "fast mode" for these kinds of PRs? Spending n times 5h of compute for getting an incremental build seems quite wasteful to me. Additionally you and I spent quite some time to get all the tests to pass here.

[MarkEWaite]

@timja have you considered adding a "fast mode" for these kinds of PRs? Spending n times 5h of compute for getting an incremental build seems quite wasteful to me. Additionally you and I spent quite some time to get all the tests to pass here.

One way to reduce the time to generate an incremental build is to modify test/pom.xml in the pull request as follows:

diff --git a/test/pom.xml b/test/pom.xml
index 17ce252f89..3135694535 100644
--- a/test/pom.xml
+++ b/test/pom.xml
@@ -52,6 +52,8 @@ THE SOFTWARE.

     <!-- Filled in by maven-hpi-plugin with "-javaagent:/path/to/mockito-core-<version>.jar" -->
     <jenkins.javaAgent />
+
+    <test>hudson.AboutJenkinsTest</test>
   </properties>

   <dependencyManagement>

That is under the control of the developer submitting the pull request.

The other acceleration technique for incremental builds would require changes to the Jenkinsfile to disable the Windows build and disable the acceptance test harness. That is not under the control of the developer submitting the pull request unless they are already a maintainer of Jenkins core. An example of that technique is available at https://github.com/MarkEWaite/jenkins/tree/fast-incremental

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[timja]

@das7pad if this is ready could you update the description please

[das7pad]

@das7pad if this is ready could you update the description please

Done. Thanks for removing the WIP changes and kicking off a build!

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

[A1exKH]

LGTM.