Thanks Alex und Eric you for the answers. I had considered writing my first pipeline job, but then I stayed on the familiar path. With the help of the Copy Artifact plugin, I copy the results and parse that in bash.
Regards, Micha Am Mittwoch, 26. Februar 2020 19:36:51 UTC+1 schrieb Eric Pyle: > > Extending on Slide's idea, you can write the result to a file in the > workspace and save that file as a build artifact. Then in the downstream > job that runs on the master you can retrieve the artifact from the upstream > job (copy artifacts from other job) and read the value in your bash script. > Or similarly, if you write the file in the upstream job as a properties > file "VARNAME=$value" then you can use that file to set a parameter to pass > to the downstream job (parameters from properties file). > > Eric > > On 2/26/2020 8:26 AM, Michael Renner wrote: > > Moin, > > > [...] > > > -- > Eric Pyle > Siemens Digital Industries Software > Simulation and Test Solutions, Product [email protected] > <javascript:>https://www.sw.siemens.com/ > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/14c6be16-531c-4721-bf79-4af5e3bb6bdb%40googlegroups.com.
