tfsbuild

I have a TFS 2013 server with several TFS team project collections and developers working happily against them. The project collections have a set of TFS builds associated, including relevant CI builds which trigger on each check-in, or in some cases, rolling (accumulated) check-ins. This process works flawlessly and has been the way of working for several years. Recently, we've introduced a Git repository into the mix which also sits on our TFS 2013 server and appears as a node that I can connect to from my development environment when I connect to my TFS 2013 server. (i.e. it's not a local

I want to build with maven my java projects on TFS Build Server. TFS Build Definition use invokeprocess in workflow. invokeprocess able to run powershell script and command batch file. Maven build successed with " mvn assembly:assembly -P prod " command in windows command prompt. But does not success in powershell. (I connected to server with remote and executed on powershell ise) (either as a regular user or as an administrator) I installed Maven 3.1.1 and Java Dev Kit 6 update 45 on Windows 2012 Standart 64-bit machine.We use NTLM authentication and proxy. I defined following configuration:

Is it possible to pass wildcard testcontainer values to the command-line mstest.exe rather than manually hardcoding multiple testcontainer values? Such as Mstest.exe /testcontainer: tests .dll I'm wanting to manually invoke mstest in our tfs 2012 upgrade template.xaml build processso tthat it behaves like a autodiscovery way similar to running tests in default template.xaml If not could this be written into a bat script to loop through folders from a given start folder? oɔɯǝɹ MSTest doesn't take a wildcard parameter for the testcontainer ( look here for a reference on the command line options

I am setting our build/release environment using TFS 2017. I set up the Build to run automatically after each commit, and when we are ready to release a version of our application, a Release is manually created, and then deployed to various environments. We would like to tag released versions in our git repository in order to easily know which git revision correspond to a binary. The "Label Source" setting in the Build definition allows to tag a git revision at build time, but since we build on every commit that would generate a lot of tags which we don't care about (as they are not deployed

If I am creating a build definition, I can’t choose a Default agent queue. Not so long ago, I can create build definition which includes the default queue. I don’t know what the change was, that it doesn’t work anymore. If I go to edit a correct created build definition and then I try again to create a definition, I can choose the default queue. What is the reason for that? Editing an existing build definition before creating isn’t the solution, because I have many projects and some have a correct build definition and some have no build Definition. If you are meaning the Default agent queue