Good question! If we were using the intermediate files (on Linux) just for
that build, we could certainly do what you are suggesting.
In our use patterns the intermediate results can be reused by several
downstream jobs. As a result we don't want to delete them at the end of the
first build that
Must be missing something. Why can't you just:
* upload files
* process them
* download resulting files
* clean up everything
In the same go?
Cheers
Le 14 mars 2016 6:09 PM, "Ioannis Moutsatsos" a
écrit :
> I have a job that uploads user data on a Linux server where it gets
> processed (ssh rem
I have a job that uploads user data on a Linux server where it gets
processed (ssh remote execution build step). Results (artifacts) are
subsequently downloaded and archived on the windows Jenkins server.
How can I delete the user data on the Linux server when their associated
Jenkins build is