I am having trouble getting my builds to run when using MSBuild in Team Foundation Server 2015. We are hosting the application on an internal server. I have configured the Controller and Agent, which seems to be okay. The "Visual Studio Team Foundation Build Service Host 2015" service is running.
When I try to queue the build, I get the following message, even though I am not using Visual Studio Online:
When I ckick OK, the build seems to be queued, but I see the following message forever:
Can anyone tell me what I am missing?
It looks like you are attempting to build a Vnext build and not a Xaml type build. You will need to set up the Vnext agent in order to get that to work. I personally use both Xaml and Vnext builds
Hope this helps!
Your build agent service is not start. Click Properties under your agent.Mark the "Build agent service is enabled"
The normal state of build control and build agent should look like as below:
Related
I recently moved my TFS to a new server.
After installing everything and setting up a new Agent my builds got the following error:
Error MSB3482: An error occurred while signing: SignTool.exe was not found at path \signtool.exe.
On my other server (Running VS 2015 and TFS 17 RC) everything worked like a charm.
I then made sure Visual studio 2017 also installed the Windows 10 SDK because in the Developer command prompt typing: 'where signtool' didn't work.
But now it does:
My TFS build still gives me this error.
It's weird that the path is to my Application solution folder and not the signtool actual location.
Does anybody have any idea on what this issue might be?
Also make sure you have installed the related .NET Framework. Take a look at this similar question: An error occurred while signing: SignTool.exe not found
Try to build locally in your build agent to see if you still got the same error.
If the build is successful locally, suggest you reconfigure or reinstall the build agents. The build agent will not detect the environment changes after you installed it. It will only detect during the installation. If you are using vNext build agent, also try to manually add some capabilities in Settings- Agent Queues- Agent Pool - Agent- Capabilities. After this trigger the build again.
We are attempting to upgrade our rather old TFS environment from TFS2008 to TFS2015. The upgrade of the server and database is not a problem and is fine.
The issue is our build machine. This is still a Windows 2003 Server that is running Visual Studio 2010 and VB6. We still have a need to use this build machine to build legacy VB6 projects. We have installed the TFS2010 XAML build controller on this server and successfully connected it to our test TFS2015 server. However when we try to run a Xaml build, (any Xaml build regardless of whether it builds VB6 or .NET) we get the following error message almost straight away.
TF900560: Could not start build: Cannot set unknown member 'Microsoft.TeamFoundation.Build.Workflow.Activities.TfsBuild.TargetsNotLogged'.
The XAML build are using the 'UpgradeTemplate.xaml' template and using the TFSBuild.proj we used under Visual Studio 2010.
We have a also set up a TFS2015 build controller on another (Server 2012) machine and that successfully starts the build process. However, our VB6 projects use a lot of third party components that will not install on Server 2012 so we can't use that.
Has anyone ever set up this kind of arrangement before? Is there anything we are missing or are doomed in this scenario? Obviously, we'd like to move away from VB6 apps, but that is not possible in the medium term.
I have a new TFS 2013 instance with its own build server that compiles a solution and deploys a database project without error. I added an MS build activity for deploying the web application projects in the solution to a target server, and that activity appears to execute without error, but nothing is actually published in the target.
Running the same publish profile from within Visual Studio on my local machine works properly. I dont know if it is missing some dependency (Web deploy 3.5 is installed on both the build and target servers, I am reinstalling VS 2013 on the build server).
Are there any specific steps/prerequisites required to make this work correctly on a TFS 2013 build server? I cannot find anything on the web other than "Install VS and MSDeploy".
I have this all working properly on a 2010 build server.
After much testing and enabling diagnostic level logging, I found that the build activity was trying to use VS 2012 (version 11) activity targets for these VS 2013 (version 12) projects. (VS 2010, 2012, and 2013 have been installed on this server to support various build activities)
In the activity specific log file this looks like this...
CodeAnalysisTargets = C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\CodeAnalysis\Microsoft.CodeAnalysis.targets
This was causing the build process to log...
_DeploymentUnpublishable
Skipping unpublishable project
...and skip the publishing.
To fix this, I set the ToolVersion property of the MSBuild activity to "12.0" and re-ran the build
Please pardon a newbie's question about MS TFS and Visual Studio 2012, I hope I'm using the correct vocabulary.
Our shop has recently moved to MS TFS and Visual Studio 2012 to build internal web services for integration. Currently we have a TFS 2010 Server running on Server2008R2 and a Build server on a Windows 7 box, our dev application server is also running Server2008R2. I have been given the job of getting a nightly build and deployment running. I have the build definition working but the deployment portion is not functioning. I have installed Web Deploy on both the dev application server and the build server as per these articles:
http://www.kevingao.net/version-control/how-to-auto-deploy-web-application-with-tfs-build-server.html
and
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
We have configured an user, web_deploy_dev in active director and that user is a local admin on the dev app server.
The parameters added to the build definition are:
/p:DeployOnBuild=True
/p:DeployTarget=MsDeployPublish
/p:MSDeployServiceURL="https://PA-APPSRV1-DEV:8172/msdeploy.axd" /* double quotes not in original code */
/p:DeployIISAppPath="DW/DWServices" /* E:\Webroot\DW\DWServices */
/p:CreatePackageOnPublish=True
/p:MsDeployPublishMethod=WMSVC
/p:AllowUntrustedCertificate=True
/p:UserName=migp\web_deploy_dev
/p:Password=******
I suspect that MSBUILD is not even calling msdeploy.exe as I see no errors in the windows event and application logs, but I do not know all the places to look. I can use a web browser and connect to the service on the dev app server as the web_deploy_dev user from the build server, I receive a web page not found error after inputting user name and PW, but I assume that is to be expected.
I am at a loss as to where to look next, I've tried searching the web but nothing I try seems to work.
Thank you in advance for your help and input.
Roy
It sounds like you are experiencing a problem where your build completes and claims success, but you aren't getting any error and nothing is actually deployed. When I've experienced this with my TeamCity build server, the problem was that MSBuild was not set up on the machine that would do the building and deploying. These are my steps to resolve the problem I think you might be having:
Make sure that at least Visual Studio Express is installed. you can tell if a full enough version of Visual Studio is installed by navigating to the
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\ directory. If you see folders like 10.0, 11.0, or '12.0', look inside them and verify that there is a Microsoft.WebApplications.targets file. Note the versions that pass that check.
In your Build Configuration, add a /p:VisualStudioVersion=12.0 or whatever version of Visual Studio is appropriate.
Let me know if this gets you anywhere or not. I'm really curious to hear if you are finding any errors or logs anywhere. Basically, in my experience using Web Deploy and MSBuild with TeamCity, if the machine that is building and deploying doesn't have the MSBuild installed with the Microsoft.WebApplication.targets file, it silently fails.
Our final build server does not have Visual Studio 2010 installed. It uses the MSBuild.exe from the .NET 4 SDK. As part of our code delivery process to our customer we need to allow him to build the projects from the command line on a Visual Studio 'agnostic' server and also to run Code Analysis rules on that machine.
On the visual studio side we started out with AllRules.rules and created exceptions going foreward so naturally we'd like the exceptions to carry over to the code analysis on the build server.
Is this possible ?
Thanks in advance.
Using standalone FxCop you can customize your CI process as you wish. Open this link and go to "Setting up continuous FxCop code analysis" chapter.
Link above seems to be dead now. You can try to look here on this SO question