Not sure what does "treat the workspace as private" exactly mean. If it's private, why can URL " *http://<jenkins_host>:<jenkins_port>/job/<job_name>/ws*" display those info?
And Yes, we archived the files after the build completes. However this is not enough -- users want to get those files when build is running so that he can know the test progress and responses in real time. Any suggestions to implement this? On Tuesday, October 9, 2018 at 9:18:55 PM UTC+8, Jesse Glick wrote: > > On Tue, Oct 9, 2018 at 12:53 AM 'Xiaocheng Wang' via Jenkins > Developers <jenkin...@googlegroups.com <javascript:>> wrote: > > we have an Java application that calls Jenkins REST API to trigger > builds. Due to project needs, we want that application to get the slave > workspace folder content when build is running. > > This sounds inherently unreliable. Treat the workspace as private. If > you want some files from a build, archive them. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b293e9ac-03b1-4e9e-895f-e86a185e33bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
