Jesse Glick

This would be better put on hold until https://github.com/jenkinsci/jenkins/pull/4623 is merged, or exclude `doCheckXXX` methods, or exclude them unless the Jenkins version indicates that https://github.com/jenkinsci/jenkins/pull/4623 is included.

Agreed, it is fine so long as the docs guide users to use `@POST` rather than the HTTP method currently being sent.

The `junit` plugin would need to parse error messages and stack traces for filenames and line numbers. How to do this is not always obvious. In the case of Java,...

Maybe. The file format is poorly standardized and each test harness will have its own conventions for how filenames are reported, so the plugin would need to use some heurstics.

> Is there a value in annotating one that hasn’t changed? Generally not, but currently GitHub will display the annotation regardless and you cannot turn this off except by pressing...

> the test file Note that a stack trace (or whatever you have, depending on language & framework) may refer to multiple lines in multiple files, both production sources and...

> something atm that is just eye-candy Well, this _could_ be really useful. If in a PR you write a test which fails in CI, or if some code you...

https://github.com/jenkinsci/parameterized-trigger-plugin/pull/235/checks?check_run_id=5243312168 smells like a too-aggressive timeout?

Probably just some flaky test unrelated to your PR.

> do you have guidance on how to implement mirroring of pipeline logs both in the Jenkins Home and in a remote storage? This can be done in a `LogStorage`...