0

We have TFS 2017 and installed build agent on Mac, connectivity is ok, our build definition does not pull all files, added Project Collection Build Service or Project Build Service roles to code security, no luck.

Thanks

Narayan Putrevu
  • 1
  • Could you check the **mappings** in the repository option of your build definition? If there are something cloaked or the setting is just not pull all files. – PatrickLu-MSFT Jan 25 '18 at 02:35
  • I am trying to map root folder, deleting workspace everytime, just does not pull all files – Narayan Putrevu Jan 25 '18 at 17:25
  • Could you provide some more information to help us debug this? Which version control are you using , TFVC or GIT? Are the files which not pull down steady or just randomly if you build multiple times? Have you tried some other build definition on the Mac Agent, did this only occurs on the specific build definition? – PatrickLu-MSFT Jan 26 '18 at 09:01
  • Can you share the build logs? – Eddie Chen - MSFT Feb 02 '18 at 01:05

1 Answers1

0

Not sure if the issue happen always for this build definition or intermittently. Try to give your build service account enough permission such as local administrator on your Mac machine. Make sure you have set the workspace clean=ture.

You could also disable the default get source steps in the build definition. And use your own script to do the get source/pull files to see if you get the same situation. How to please follow: Is it able to ignore/disable the first step Get source in vNext Build?

Try to run the build multiple times, check if there are steady of some files which not pull down or the files are just randomly. Check the left-over space on your Mac hard driver is sufficiently.

If all of the above still not fix the issue, suggest you reinstall/ reconfigure your Mac build agent(use the latest version) and try again. There is a thoroughly tutorial: Deploy an agent on OSX in official.

PatrickLu-MSFT
  • 49,478
  • 5
  • 35
  • 62