Skip to content

Reduce build output size from 26 GB #3937

Open
Task
Open
Reduce build output size from 26 GB#3937
Task
Assignees
vukelich
Labels
Central-EngSysengineering itemneeds-team-attentionWorkflow: This issue needs attention from Azure service team or MCP team.server-Azure.McpAzure.Mcp.Servertools-CoreAZMCP Core functionality that all other tools build on top of

Description

@vukelich
Steven Vukelich (vukelich)
opened on Oct 13, 2026

Most of the test Azure.Mcp.Tools.*.Tests.csproj files have a project reference to the Azure.Mcp.Server.csproj project. Today, the project references are copying the entirety of the Azure.Mcp.Server.csproj build output to the test project's output. That means a full build of the Microsoft.Mcp.slnx bloats to 26 GB due to over 40 copies of the Azure MCP server. This can be solved with a combination of tinkering of our MSBuild files and unit test code to run the Azure.Mcp.Server.exe file from a single directory.

Activity

  1. Steven Vukelich (vukelich)
    self-assigned this
    on Oct 13, 2026
  2. Steven Vukelich (vukelich)
    added
    Central-EngSys
    on Oct 13, 2026
  3. Steven Vukelich (vukelich)
    added the
    Task
    issue type on Oct 13, 2026
  4. github-project-automation
    added this to Azure SDK EngSys 🚀🌒🧑‍🚀on Oct 13, 2026
  5. github-project-automation
    moved this to 🤔 Triage in Azure SDK EngSys 🚀🌒🧑‍🚀on Oct 13, 2026
  6. github-actions
    added
    needs-team-attentionWorkflow: This issue needs attention from Azure service team or MCP team.
    server-Azure.McpAzure.Mcp.Server
    tools-CoreAZMCP Core functionality that all other tools build on top of
    on Oct 13, 2026

  7. github-actions commented on Oct 13, 2026

    @github-actions
    github-actionsbot
    on Oct 13, 2026 – with GitHub Actions
    Contributor

    Thanks for your feedback! Steven Vukelich (@vukelich) is looking into it.

  8. vukelich commented on Oct 13, 2026

    @vukelich
    Steven Vukelich (vukelich)
    on Oct 13, 2026
    MemberAuthor

    5. Thanks for your feedback! Steven Vukelich (@vukelich) is looking into it.

    Thanks, Steven Vukelich (@vukelich)!

  9. github-actions
    added
    engineering item
    on Oct 13, 2026

  10. github-actions commented on Oct 13, 2026

    @github-actions
    github-actionsbot
    on Oct 13, 2026 – with GitHub Actions
    Contributor

    Triaged as engineering item because this is internal build/test infrastructure work to reduce duplicated Azure.Mcp.Server output in test builds rather than a user-facing defect or net-new feature.

    • Classification: engineering item
    • Additional labels: No new special labels added; the existing area labels (server-Azure.Mcp, tools-Core, Central-EngSys) already capture the scope well.
    • Priority: Medium — the 26 GB build output is a meaningful engineering productivity and build-efficiency problem, but this issue does not currently read as a repo-wide blocker or active CI incident.
    • Issue Type: Task
    • Owner recommendation: Steven Vukelich (@vukelich), because the issue is already scoped with a concrete MSBuild/test-output direction and sits closest to Azure MCP server/build-system internals.

    Generated by Issue Triage Agent for #3937 · copilot · gpt54 · 14.9 AIC · ⌖ 6.46 AIC · ⊞ 26.9K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Central-EngSysengineering itemneeds-team-attentionWorkflow: This issue needs attention from Azure service team or MCP team.server-Azure.McpAzure.Mcp.Servertools-CoreAZMCP Core functionality that all other tools build on top of

Type

Task

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions