Hi,I am trying to run a build, but the build seems to be stuck with a state of Stage Awaiting Agent. I have looked at the agent compatibility matrix and it’s having a problem finding Visual Studio 2013. Now this makes sense because I have a Build stage that attempts to build a VS2013 solution file and I don’t have VS2013 installed on the agent machine. But, I would have thought that the build will fail stating the absence of VS1013 as the reason for the fail. Instead the build just seems to sit there.Is this by design? At the moment I need to manually cancel the build process.Thanks
This is by design, if we failed builds because an agent wasn’t available, people would be having a lot failed builds. This is because there are a number of reasons an agent might not be available, they might all be busy (you can limit how many concurrent builds an agent can run), you might not have enough licenses, the agent machine may go down for windows update…
What will happen, is once you install whatever is missing (ie VS2013) the agent will report that to the server and the build will start. FWIW, you may not need VS2013 installed, if it’s a .net project then most of the time you can just use the MSBuild action. The VS2013 action calls devenv which is part of VS2013, really only needed for C++ and some other special cases.