Skip to main content

View builds across multiple projects

One very annoying thing in Team Foundation Server 2010 is that you can only see the builds for 1 team project in Team Explorer. This is especially a problem when you are running many builds and you want to know which builds are already queued/running.

Luckily this is really easy to create yourself using the TFS object model.  Create a simple console application in Visual Studio and add the following code:

 

   1:  using Microsoft.TeamFoundation.Client;
   2:  using Microsoft.TeamFoundation.Build.Client;
   3:   
   4:  var tfs = TfsTeamProjectCollectionFactory.GetTeamProjectCollection(new Uri("http://myTFS/MyCollection"));
   5:  var bs = tfs.GetService<IBuildServer>();
   6:  var qbSpec = bs.CreateBuildQueueSpec("*", "*");
   7:  var qbResults = bs.QueryQueuedBuilds(qbSpec);
   8:   
   9:  foreach (var qb in qbResults.QueuedBuilds)
  10:  {
  11:      var status = qb.Status.ToString();
  12:      var def = qb.TeamProject + @"\" + qb.BuildDefinition.Name;
  13:      var pri = qb.Priority.ToString();
  14:      var datequeued = qb.QueueTime.ToString();
  15:      var requestedBy = qb.RequestedBy;
  16:   
  17:      if (qb.RequestedBy != qb.RequestedFor)
  18:      {
  19:          requestedBy = qb.RequestedBy + " (for " + qb.RequestedFor + ")";
  20:      }
  21:      Console.WriteLine("{0} {1} {2} {3} {4}", status, def, pri, datequeued, requestedBy);
  22:  }
  23:   
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more