Austin Agile DevOps

DevOps in the Cloud
posts - 70 , comments - 7 , trackbacks - 0

July 2014 Entries

Move TFS 2013 Git Repo to a Different Team Project
1. Go to the target team project admin site 2. Create the new repo on the TFS server (with the same name as the source repo except under the target team project) 3. Go to the target team project site and display the empty repo. Note the new repo remote url 4. Open Visual Studio 2013 team explorer connect tab (Update 2 or >) and connect to the remote source repo 5. Clone the repo under the new team project or other location 6. Right click on the new (cloned) local repo and click Open Command Prompt ......

Posted On Friday, July 25, 2014 12:34 PM | Comments (0) |

TFS 2013 Build Process Template – Change the “AutomatedTest” Argument Default Value
It should be simple, but due to the length of the string, the syntax was not obvious. The out-of-the-box default is as follows. Note the backslash escape character and stick to the syntax: {New Microsoft.TeamFoundation.Bu... { ""AssemblyFileSpec"": ""**\\*test*.dll;**\\*test*... ""RunSettingsFileName"": null, ""TestCaseFilter"": """", ""RunSettingsForTestRun"": { ""ServerRunSettingsFile"": """", ""TypeRunSettings"": ""Default"", ""HasRunSettingsFile"": false }, ""HasRunSettingsFile"": ......

Posted On Tuesday, July 8, 2014 12:56 PM | Comments (0) |

Nuget Push to Klondike Requires Packages Appended to Source and SetApiKey URL
When we upgraded to NuGet 2.8 our PUSH command starting failing. The first fix was to appended “packages” to the source URL string like this: We use the SetApiKey command on our server so we don’t have to explicitly include the API key itself in the push command. After making the change above we had issues with the PUSH command not finding the API key. To fix this, we appended “packages” to the source argument of the SetApiKey command like this: nuget setApiKey myApiKey ......

Posted On Tuesday, July 8, 2014 10:47 AM | Comments (0) |

Powered by: