tfs2015

TFS 2015 Publish Build Artifacts in one directory

蓝咒 提交于 2019-11-28 03:05:06
问题 We have just upgraded from TFS 2010 to TFS 2015 and I'm recreating a XAML-Build-Definition in the "vNext" build/workflow-format. In the old Build it was possible to output all files (the DLLs) flat in one single directory, without their original directory structure. Is this still possible with the new TFS 2015 Build framework? I have the following Publish Build Artifact -Settings: Artifact Type: File Share Path: \\server\tfslib\$(Build.DefinitionName)\$(Build.DefinitionName)_$(Build

TFS drop, exclude obj folder using minimatch pattern

淺唱寂寞╮ 提交于 2019-11-27 22:13:15
问题 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

Error 'No agent could be found with the following capabilities: msbuild, visualstudio, vstest'

北慕城南 提交于 2019-11-27 20:57:52
I'm setting up a new build server using TFS 2015 and after I configured the agent, when I tried to queue a build I got this error: No agent could be found with the following capabilities: msbuild, visualstudio, vstest How can this be resolved? Install Visual Studio on your build agent, then restart the build agent. Restarting the build agent will capture the added Capabilities. Simon_Weaver Note: First of all, you can do all this with the community edition and TFS Express 2015 on your own server (for free up to five users) - so don't worry about needing to use the Visual Studio online version

TFS 2015 REST API Authentication

别等时光非礼了梦想. 提交于 2019-11-27 16:02:53
We are trying to invoke the TFS 2015 REST API's from a web-page using Javascript and have a challenge in establishing valid authentication with the TFS server. We do not know how to generate a personal access tokens or an OAuth access tokens. The instruction below seem to apply more toward VSO than on-premise TFS. https://www.visualstudio.com/en-us/integrate/get-started/rest/basics How can I generate an authentication key/token? UPDATE: As on Mar 2017, the latest release of On-Prem TFS supports creating personal access tokens for all users. Using the below javascript code by @Elmar you can

TFS 2015 Can build variables access other build variables?

非 Y 不嫁゛ 提交于 2019-11-27 14:45:15
问题 When I define a custom variable in the new TFS 2015 team build as follows: Name: SomeOutput Value: $(System.DefaultWorkingDirectory)\Some ...it doesn't seems to expand $(System.DefaultWorkingDirectory) . Is there a way around this? EDIT: At least it seems it's not expanded everywhere. For example, in MSBuild-Arguments, /p:OUTPUT="$(SomeOutput)" is expanded to /p:OUTPUT="C:\TfsData\BuildAgents\_work\3\s\Some" but when i add a cmd line build task with tool set to cmd and parameter set to /k set

No build notifications with VS 2015?

怎甘沉沦 提交于 2019-11-27 13:29:02
问题 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 .. 回答1: The BuildNotificationApp is still a part of the VS 2015 and can be

Where can I find Microsoft.TeamFoundation.Build.Client in Visual Studio 2015?

半城伤御伤魂 提交于 2019-11-27 11:34:10
I have a clean windows installation with just Visual Studio 2015 installed and I'm looking to find the Microsoft.TeamFoundation.Build.Client assembly? I'm wondering if it has now been made obsolete with the upcoming vNext Build or if the namespace moved? or something else? The MSDN documentation only goes up to Visual Studio 2013 and search for the dll on disk produced no results. when I move to VS2015 and TFS2015 id wish to continue to use the classic build system - I guess I could use the rest API in TFS2015 but rather not have to port all the code of our custom activities and MSBuild tasks

How to chain builds in TFS 2015?

耗尽温柔 提交于 2019-11-27 09:35:23
Is there a way in TFS 2015 to have two builds such that the second build gets triggered whenever the first one finishes (successfully)? There are solutions for the old XAML based build system, but nothing for the new script-based system, which is what I'm using. This question pops up every now and then. The official docs literally say "not yet" (see the last Q&A entry). There's also an ancient suggestion on UserVoice , which is in the Planned state since March this year. That's quite promising and lets me hope this will be implemented in vNext build system the first thing. I achieved the

TFS-2015 limiting user list

微笑、不失礼 提交于 2019-11-27 08:46:05
问题 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? 回答1: In many organization,

vNext build on TFS 2015 hangs on MSBuild step and produces no log files

∥☆過路亽.° 提交于 2019-11-27 08:10:23
问题 We have recently upgraded from on-premises TFS2013 to 2015 Update1, and we have set up a VSO Build Agent. I am now trying to set up a test (continuous integration) vNext build for a solution in our Git repository, but the builds are not running and not producing any logs . The build properties have been set up to indicate the correct Git repo, and the following three have been added to Variables: VSO_GIT_USERNAME, VSO_GIT_PASSWORD, DNXPath. MSBuild is the only step added to the build at the