Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: copy-to-slave-plugin
-
Labels:
-
Similar Issues:
-
Epic Link:
Description
CopyToSlaveBuildWrapper looks like it could be made compatible with Workflow (implement SimpleBuildWrapper) without major refactoring. (Unclear to me why this is a BuildWrapper rather than a Builder.) Similarly, CopyToMasterNotifier could be made to implement SimpleBuildStep. (Again unclear why this is a Publisher rather than a Builder.)
Attachments
Activity
This would allow you to Stash world-readable files on the master without exposing secrets
Basically $JENKINS_HOME should not be readable to other users.
Hi,
Is there any update on this feature , using copy to slave plugin for pipeline jobs if so please let us know
Also hope this copy to slave plugin can work for pipeline jobs. Seems that now we don't have any good function to copy big files from master to slave before build.
Jay Z
added a comment - Also hope this copy to slave plugin can work for pipeline jobs. Seems that now we don't have any good function to copy big files from master to slave before build. 
Jan Bijota
added a comment - Hi Vivekanand SV , is there any update about this issue?
Thanks,
Jan 
That makes sense for public Jenkins; I don't see anything inherently dangerous about this in a Jenkins with authentication inside an intranet/VPC (though I agree it is less secure). Regardless, you can also accomplish a similar thing by running a separate agent on the master with a different user or in a container, and thus having the unix security model to isolate things as desired. This would allow you to Stash world-readable files on the master without exposing secrets, unless there are other concerns I'm not aware of, which I fully admit there might be.