I got the problem, that Conan fails, because he got an error '500', when uploading a package.
Unluckily Conan is (at the moment) not retrying the task, as I put him on the commandline arguments.
So I wrote the following groovy script for Jenkins Pipeline:
The script is working, so that Jenkins build the job (also when the first upload fails). But unluckily he still recognize the first error in the upload as error of the complete job. I thought, when I catch the error, he should ignore the failure. The "currentBuild.result" is already set to "FAILURE" instead of "SUCCESS".
Could it be, that the Artifactory plugin first catch the error, then set "currentBuild.result" to "FAILURE" and then rethrow the execption?
May be it would be fine, if we have an extra flag to let the artifactory plugin just not to write the currentbuild.result?