Skip to main content

Community TFS Build Extensions: December release

Just before the year ending, a new version of the Community TFS Build Extensions is released. This release contains 100 Activities / Actions for Team Foundation Build 2010 and Team Foundation Build 11.

New in this release is the Community TFS Build Manager. It is intended to ease the management of builds in medium to large Team Foundation Server environments, though it does provide a few features which all users may find useful.


Current Feature Set

  • View and sort Builds and Build Definitions across multiple Build Controllers and Team Projects
  • Bulk operations on Build Definitions
    • Change Build Templates
    • Queue
    • Enable
    • Disable
    • Delete
    • Set Retention Policies
  • Clone Build Definitions (includes workspace mapping translation)
  • Create a DGML image of your Builds and Controllers
  • Bulk operations on Builds
    • Delete
    • Open Drop Folders
    • Retain Indefinitely
The Community TFS Build Manager is now available on the Visual Studio Extensions Gallery
A blog post by Jakob Ehn describing the features of the Community TFS Build Manager can be found here
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