I have been researching but can't seem to find anything on uninstalling a build agent from Teamcity. I have read that if I can stop the service there should be a 'Remove' button that appears under that agencies summary section. I have tried stopping the service through Server Manager, as well as, running the service.stop.bat under the <agent>\bin, but have had no success with the button appearing. Is there an easy way to remove the build agent from Teamcity?
Current Teamcity version: TeamCity Professional 10.0.3
Have you checked buildAgent/bin folder? There should be uninstall.bat file, which, I assume, should do just what you want.
Related
After updating TFS to update 2, in the CI build tasks "IIS Web App Deployment" is marked as Deprecated. Whats the replacement for this task?
Also in the CD in the after adding "IIS Website Deployment Template" the IIS Web App Manage and IIS Web App Deploy tasks are marked with
This task is no longer installed. Re-install the task or remove it from your definition.
I just love it when Microsoft changes things out of the blue without clear, available documentation!
It looks like they deprecated these to make way for Marketplace apps. You should add the first one in the list, "IIS Web App Deployment Using WinRM".
https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.iiswebapp
I've no idea why this isn't "installed" in TFS by default, since it is Microsoft's own solution. Instead, you get the pleasant experience of:
Realizing midway through your Release configuration that the one you were used to using is now suddenly deprecated
Researching the replacement on SO
Clicking "Get Now" on the new IIS Web App Deployment Using WinRM item.
Adding it to your TFS account, presuming you have access to do so without having to kick the request up the chain to your TFS instance owner or manager.
Saving your release pipeline in progress, because TFS doesn't "see" that you have the new IIS Web App Deployment Using WinRM item until the whole pipeline task creator reloads.
Finding and re-opening the pipeline in progress you just saved, only to re-open it and continue editing to complete your initial task.
Cheers!
So I'm currently trying to play around with Team Foundation Server 2015 on premise. I got source control down and already setup my project collections and team project.
My next adventure is to try out continuous integration starting with Automated builds. I am however stuck in Build definition.
I already have an online build agent with the following specs:
Windows 7
Visual Studio 2013
Now when I que a build it fails after the following message
Waiting for console output from an agent...
I tried to download the log files but it gave me a blank folder. Do not know what next steps I should check and would really appreciate any help in this area.
Thanks
Generally this issue is caused by the agent failing to access resources for the build process.
Please first check if the agent is enabled in your Agent Pool, then try below things:
Check the connectivity
Check URL configuration of TFS as Danko mentioned above, make sure you deployed the build agent with the correct URL.
Try disable the Firewall on machine to check if the communicate issue caused the build hang.
If you are set the specific port or use proxy server for your TFS, then try to set the exception for the port on your firware. See this similar issue.
Make sure the account that the agent is run under is in the “Agent
Pool Service Account” role.
Make sure you deploy the Windows build agent by exactly following
this article.
Restart below services .
Visual Studio Team Foundation Background Job Agent
Your build agent service
Deploy a new build agent to check if that works.
Reference this similar thread for details:
2 Solutions collect form web for “vNext build on TFS 2015 hangs on MSBuild step and produces no log files”
Run Get-NetFirewallPortFilter in PowerShell (run PowerShell as
Administrator) on the TFS machine to get the port exception list.
Run the following PowerShell script to set exception for the specific
port:
$port = New-Object -ComObject HNetCfg.FWOpenPort
$port.Port = 9191
$port.Name = 'TFS CI Port:9191'
$port.Enabled = $true
$fwMgr = New-Object -ComObject HNetCfg.FwMgr
$profile = $fwMgr.LocalPolicy.CurrentProfile
$profile.GloballyOpenPorts.Add($port)
After installing the agent, it would have to appear Green, Enabled and in an IDLE state - in your WebAccess (Settings, either Build or Agent Queues directly, and verify the state there). I have experienced only once similar behavior, with accessing the resources and it was connected with how the TFS Server "Web Access URL" was set in the TFS Administration Console.You should make sure, that you are able to access your TFS from the build machine, using the exact same URL, that you have provided to your new build agent as well.
Recently, I have been facing this issue where my TFS(2015 update 3) msbuild runs with old code even after checking in changes and saving changes locally in visual studio 2015 enterprise edition. I use build to run Automated UI test by running my machine as test agent.
I can see an agent workspace other than my workspace(don't know if anything to do with it).
Can anyone guide me to correct this issue, or anyway to move forward without facing this issue again?
Please try below items to narrow down the issue:
Check the source code via web portal, verify that the new changes are
really checked in.
Check the definition setting, try to set "Clean" to "True" in
Repository tab.
Also enable the "Clean" option in MSBuild step.
Try to create a new definition with the same settings, then try it
again.
Clean the caches for your TFS Application Tier and agent machine,
then try it again.
Reboot the TFS and agent machine
UPDATE:
Below screenshot for your reference, also make sure you mapped the source correctly. You can also try to delete workspace and entire source folder directly from your agent machine, eg C:\Agent\_work\2\s (You can get the info from build log)
I'm writing Protractor/Jasmine E2E tests on a local machine in Visual Studio 2015 which has my project stored through TFS and then I am running those tests each night on another machine. I may be misunderstanding the concept here and/or missing the point of the appropriate tool for this situation.
But, is there a way such that when I check in changes on my local machine that those changes are automatically checked out (get latest) on the secondary machine without having to manually get latest on the files?
If you deploy a build agent on the second machine, when you queue build, build agent will get latest version of your project into the source directory.
Or as #jessehouwing mentioned in comment, you can use TF.exe command line in a script on your second machine to get latest version of your project:
tf get /version:T
I started learning TFS Team build. I am having a basic doubt. I referred this
article. I followed the steps exactly and got succeeded. I created a Console Application and pushed in TFS using TeamServices. My doubt is when we build a Console application in visual studio we will get an exe in bin folder.
Same way in this team build how to get the output in my local machine ?
What is the difference between the local build using Visual studio and this team build ?
EDIT :
I added like this. Still I am not able to see the output in the RELEASE folder.
I got the result as success saying
Still I couldn't figure out the output - the exe produced as a result of build.
Am I doing anything wrong ?
Note : I have a requirement like what you explained in the answer. So why I am using TFS team build. Since I am new I am experimenting with a small example.
When to use a build system
Team Build does not replace Visual Studio build. Use Team Build when you have a complex / lengthy build, to easily integrate running unit tests as part of the build or to deploy assemblies to a server after the build is complete.
Most people will setup a TFS build definition to run as "Continous Integration" build, meaning that whenever a commit is checked in, a build occurs. The build would compile and run tests and if it fails all developers can be notified.
How to get to the build output
When using a build system like TFS build, the build is done on a remote machine. If you want to retrieve the output of the build, add a Publish Build Artifacts step to your build definition. Since the build happened on a remote machine, the remote machine does not have access to your local developer machine.
The artifacts (assemblies) will be available for download on the build summary page: