ArtifactManagerFactoryimplementation plugin—these are only useful for Jenkins servers, especially with agents. For example,
unstashwould gratuitously use cloud storage! Would be more sensible to have the function packaging simply upload files from
$JENKINS_HOME/jobs/job/1/artifacts/after JFR exits.
we're running our tests in Kubernetes and wanting to report them back to jenkins, not have jenkins collect them
Does this mean you want your Jenkins-initiated test runner (whatever that is) to upload results directly to some kind of database, then have the Jenkins web UI be able to display those results in its usual way later? If so, this is theoretically possible (not a use case I had considered), though you would still need the Jenkins job to run a dummy
junit step so as to add a
TestResultAction marker to
build.xml (all details would be loaded from the external provider).
--prow). Containers using
jenkinsfile-runneror Tekton are run and pod logs are optionally copied to permanent storage (as per
jx get storage) when the build completes. Very different from JEP-207/210/212, which deals with regular Jenkins servers that should upload logs of potentially in-progress builds from agents to external storage and (as needed) retrieve from storage to the master.