Jesse Glick

> deprecating/removing `RunWrapper` will also require changes over in `pipeline-build-step` Right, mentioned in the PR description.

This PR exemplifies the reason I thought JENKINS-55410 was a bad idea to begin with—it just leads to endless creeping requests to add `label` to more and more steps, ad-hoc....

By the way I am not sure when you last tested these instructions (specifically those for workload identity), but I needed to make several modifications just for setup and it...

> Our use case involves uploading ~5,000 files from one host, and then pulling a zip (Using the Zip archive link generated by Jenkins) of those files down onto another...

_My_ next actions are to review, and perhaps rewrite a bit, once I have time to work on this plugin—it is on the back burner. But I do not recommend...

A continuation of #88, I gather. At some point I need to set aside enough time to review & test the nontrivial PRs in this plugin.

No, the onus is on me to invest in time reviewing & testing this, or finding & training an active maintainer.

> The surefire plugin acts as though the Security2779Test is being run multiple times with the same argument and treats a failure of one argument as a "flaky test". This...

> you are sent to a page with the container logs Oh, that is handy for debugging. Better IMO would be for this content to be copied to the build...

> is it possible to "mix" the build log streams with the underlying container agent logs? We already do so for the K8s event logs, or did until #1192. Not...