Skip to content

Remove pipeline run parameters for package types #1769

@hallipr

Description

@hallipr

We don't support partial deployments for a server. e.g., if the server supports docker, our server.json deployment script expects that docker is deployed if server.json is being deployed. The same is true for all of the other targets.

If we require pipeline parameters to make chunks of our yaml conditional, those parameters should be hard coded in the servers' build.yml files and not be exposed as per-run parameters to the release invoker.

i.e.
Azure.Mcp.Server/build.yml

extends:
  template: /eng/pipelines/templates/common.yml
  parameters:
    ServerName: Azure.Mcp.Server
    PublishTarget: ${{ parameters.PublishTarget }}
    RunLiveTests: true
    PackageDocker: true
    PackageVSIX: true
    IncludeNative: ${{ parameters.IncludeNative }}
    TestTimeoutInMinutes: ${{ parameters.TestTimeoutInMinutes }}

instead of

extends:
  template: /eng/pipelines/templates/common.yml
  parameters:
    ServerName: Azure.Mcp.Server
    PublishTarget: ${{ parameters.PublishTarget }}
    RunLiveTests: true
    PackageDocker: ${{ parameters.PackageDocker }}
    PackageVSIX: ${{ parameters.PackageVSIX }}
    IncludeNative: ${{ parameters.IncludeNative }}
    TestTimeoutInMinutes: ${{ parameters.TestTimeoutInMinutes }}

Metadata

Metadata

Assignees

Labels

needs-team-triageWorkflow: This issue needs the team to triage.server-Azure.McpAzure.Mcp.Servertools-SetupCatch-all for setup issues

Type

No type

Projects

Status

Untriaged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions