On Tue, Oct 9, 2018 at 10:00 PM 'Xiaocheng Wang' via Jenkins
Developers <
jenkin...@googlegroups.com> wrote:
> 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?
The workspace browser is intended only for interactive
troubleshooting. By design, the workspace is only guaranteed
accessible during the build (in the case of Pipeline, during a `node`
block), as subsequent builds may overwrite these files, and “cloudy”
agents will typically throw away the whole filesystem as soon as the
build is done.
> users want to get those files when build is running so that he can know the test progress and responses in real time.
In the case of JUnit-formatted test results, this is handled via
https://plugins.jenkins.io/junit-realtime-test-reporter
This is done as a plugin, so it uses Java APIs to access these files.