I upload files to the Artifactory successfully (albeit with error messages,
Error occurred for request GET /artifactory/api/system/version HTTP/1.1: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
Failed sending usage report to Artifactory: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
. These are possibly due to the fact that I can't specify a custom truststore for the Plugin, the Plugin doesn't use the environment of the Agent (all with the custom truststore specified), or it uses the master's environment, which needs a different truststore configuration, and I don't have access to the default truststore java uses, since it's not mine. However, the artifacts get uploaded.

I also tried to upload files with a Freestyle project. Here I used "Generic-Artifactory Integration" with the same jfrog Artifactory I configured and tested in the Jenkins main configuration and used in the pipeline, and the same filespec. I get the same certificate error messages.

However, where the pipeline project uses the artifactory upload in the post stage, the build is still marked as successful. With the freestyle project, the build is marked as failure. Therefore the plugin isn't usable with a Freestyle project. With the pipeline it's just irritating, and one tends to expect the upload to fail in the future, if it should validate the server for the upload. That it doesn't, looks more like an omission.

Possible solutions:

• Make the Plugin take its java/keystore environment from somewhere available (Jenkins master, Agent)
• If so, let me choose if Agent or master
• Make the Plugin java environment configurable
• allow me to specify the error condition or result