![]() Some other explanation, or tips how to avoid this behavior of the TFS? So it seems the TFS is caching the given path vars and did not looks for them on every build. ![]() ![]() So we executed a batch script in the same described way with just echo %path% as its content.Īfter a lot of failed builds and calling all tools via batch script and absolute path we found this article and simply restarted the TFS and everything woks like a charm. every build always showed us: 'grunt' is not recognized as an internal or external command, operable program or batch file. So we knew that the build user is understanding all given batch commands, because we also tried it with this user looged in. ![]() And everything works fine after some configurations and adding of missed path variables. We tried if npm is working, grunt is installed globally and also ruby got its sass gem. So we could install all needed Software on the TFS with the same user the TFS is using if it is building an artefact. To find out which user will be used we added a batch file with echo %username% and added the "Batch Script" task to the build process and let this task execute our script. We faced the same issue and we did the following:įirst of all we installed every software on the our system user that is also used for the build.
0 Comments
Leave a Reply. |