In the case we have a Windows Master and Linux Slaves, using usesPlugin flag, the buildinfo.properties file would get generated in master instead of agent/slave.
it turned out that .getCanonicalFilehere, makes the buildinfo.properties file path of the master filesystem instead of the slave/agent.
We passed the same stream as encrypting the file to resolve this issue.
[ ] All static analysis checks passed.
In the case we have a Windows Master and Linux Slaves, using
usesPlugin
flag, the buildinfo.properties file would get generated in master instead of agent/slave.it turned out that
.getCanonicalFile
here, makes the buildinfo.properties file path of the master filesystem instead of the slave/agent.We passed the same stream as encrypting the file to resolve this issue.
Depends on: