tfs2015

TFS drop, exclude obj folder using minimatch pattern

拈花ヽ惹草 提交于 2019-11-29 03:55:46
I'm setting up TFS 2015 on-prem and I'm having an issue on my last build step, Publish Build Artifacts. For some reason, the build agent appears to be archiving old binaries and I'm left with a huge filepath: E:\TFSBuildAgent\_work\1a4e9e55\workspace\application\Development\project\WCF\WCF\obj\Debug\Package\Archive\Content\E_C\TFSBuildAgent\_work\1a4e9e55\workspace\application\Development\project\WCF\WCF\obj\Debug\Package\PackageTmp\bin I'm copying the files using the example minimatch pattern to begin with: **\bin I'm only testing at the moment so this is not a permanent solution but how can

No build notifications with VS 2015?

这一生的挚爱 提交于 2019-11-28 21:06:16
We used to set up our dev machines to receive build notifications in the task bar. However, the process we've followed - as per this description - doesn't apply any more with Visual Studio 2015 as the Build Notification app is no longer part of the package? Any ideas what happened to it? Replacements? Work-arounds? Update 4/2016: Nothing appears to have changed with Update 2 - new build definitions still don't show up .. The BuildNotificationApp is still a part of the VS 2015 and can be found here: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\BuildNotificationApp.exe .

TFS-2015 limiting user list

偶尔善良 提交于 2019-11-28 14:44:30
After upgrading to TFS 2015 we are seeing all users in the collection being displayed as options for the Assigned To fields of a Work Item. In 2013 we had set an ALLOWEDVALUES rule set to [project]\Contributors. It would restrict the list in the drop down to only the values in that group. Now the drop down shows everyone and only complains if you try to select a user from the complete list that is NOT in the contributors groups. How do we get the old behavior back? In many organization, the work item type is shared across many teams. The old dropdown was long and was cluttered with people you

TFS 2015 SDK Missing Microsoft.WITDataStore64.dll

久未见 提交于 2019-11-28 12:02:16
I am attempting to switch to the TFS 2015 SDK dlls (Version 14) for a few reasons. First, they are in nuget and second, the 2013 SDK dlls (Version 12) require the 32-bit flag flipped in IIS. I pulled down nutget package and the namespaces all line up with the existing version 12 namespaces. Everything compiles fine and there was no error on local deployment. However, when I attempt to load projects using the WorkItemStore service. TfsTeamProjectCollection collection = new TfsTeamProjectCollection(URL); var service = collection.GetService<WorkItemStore>(); I get: Additional information: Unable

TFS 2015 as nuget server

China☆狼群 提交于 2019-11-28 11:09:19
问题 We are currently testing whether we can replace our current build server (TeamCity) with TFS 2015 Build. Does anyone know of TFS 2015 has built-in Nuget Server like TeamCity. Thx 回答1: Package Management (NuGet with npm and maven coming soon) is currently only available for VSTS. The on-premises support for Package Management will come in the next version of TFS. Source - TFS Feature Timeline for 2016 回答2: VSTS and TFS now provide built-in support for Maven Package Management to compliment its

Display OpenCover results in TFS 2015 build Summary

我的梦境 提交于 2019-11-28 10:25:21
I have generated my xml coverage file as part of CI build on the TFS server using vNext 2015 build definition. How would one display the results in the TFS 2015 summary ? Either using the xml report or the html generated using the ReportGenerator. You need to convert the results produced by OpenCover to a format which can be parsed by TFS. One way to do this would be to use the OpenCoverToCoberturaConverter NuGet package. Once you have that, you can use the Publish Code Coverage Results build step. I have described the whole process on my blog . In “TFS 2015 - Update 2” this is possible by

How to authenticate build.vnext agent to on-premise TFS

匆匆过客 提交于 2019-11-28 09:51:17
问题 We have an on-premise TFS2015RC installation. The server is part of our domain. When configuring a build agent (build.vnext) on another server in the same domain, everything works as expected. However, when configuring a build agent on a server outside of this domain, the following happens: Using ConfigureAgent.ps1: accept all defaults choose interactive mode (e.i. not installed as Windows Service) then an authentication dialog shows up: I enter a domain user ( domain\user ) which is

TFS 2015 - Delete Build Artifacts

*爱你&永不变心* 提交于 2019-11-28 09:38:16
问题 How to step up TFS 2015 Update 2 to delete artifacts when build is deleted? Is this possible? EDIT: Add retention screen shot I am using the default retention policy but it is NOT deleting artifacts from the drive. EDIT: Add Copy and Publish Build Artifacts EDIT: Add Working Folder I added a powershell to display all environment variables and it said my workingFolder = E:TfsBuilds\Agent1_WorkPlace\5\s Do you a powershell to set workingFolder to default? Here is the file structure i have: 回答1:

Modify TFS 2015 BuildNumber during build process

江枫思渺然 提交于 2019-11-28 08:29:25
问题 I have some embedded C software stored under TFS and also have a corresponding TFS build definition that successfully checks out the code and builds it using the relevant compilers. So just to be clear, although this is TFS, I'm not building a .NET application. Now that I have the build working, I'm trying to provide overall software versioning support which should be linked to the build process. My current aim is as follows: The source code that is being built has a header file that has

No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again

感情迁移 提交于 2019-11-28 06:39:58
I am in the process of upgrading our existing solution to .Net 4.6.1 and have been unable to get our unit tests to run during a server build. Locally they run as expected and flipping the framework version back to .Net 4.5.1 makes them run again on the server. I am getting the following error: No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. I have reproduced the problem in a simpler setup: Solution with a single C# Unit Test project with two tests (one failing, one passing). XAML build definition using