Skip to content

test(ci): exercise multi-deployment PR check#18051

Draft
PawelWMS wants to merge 5 commits into
pseudotrurl/pr-check-ct-test-base-4.0from
pseudotrurl/pr-check-ct-lolcat-test
Draft

test(ci): exercise multi-deployment PR check#18051
PawelWMS wants to merge 5 commits into
pseudotrurl/pr-check-ct-test-base-4.0from
pseudotrurl/pr-check-ct-lolcat-test

Conversation

@PawelWMS

Copy link
Copy Markdown
Contributor

What

  • Apply the multi-deployment Control Tower PR-check configuration from ci: run PR checks across configured deployments #18039.
  • Add the lolcat component in a separate commit to produce a real component/source change.
  • Target the temporary pseudotrurl/pr-check-ct-test-base-4.0 branch instead of 4.0.

Why

Provide an isolated draft PR for validating the updated ADO PR-check pipeline against a clone of the 4.0 branch.

Risk

Test-only PR. Do not merge. The base and head branches are temporary and should be deleted after ADO validation completes.

Verification

  • Resolved and rendered lolcat from Fedora 43.
  • Confirmed post-commit render has no drift.
  • Built lolcat-1.5-5.azl4.x86_64.rpm.
  • Inspected RPM contents and ran lolcat in an Azure Linux 4.0 mock environment.
  • Preserved two signed commits: pipeline configuration, then lolcat component.

PawelWMS and others added 2 commits July 16, 2026 19:31
Generate one parallel Control Tower job for each configured deployment
so one reviewer-gated run exercises DEV, STAGING, and PROD.

Keep each deployment's audience, endpoint, service connection, and error
policy together. Run prcheck for every deployment, make STAGING
non-blocking, and limit scratch package builds to DEV.

Reuse the DEV-specific audience and endpoint in the post-merge package
wrapper so both pipelines share one variable-group source of truth. Use
OneBranch Official because the PR pipeline accesses a production-scoped
identity.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Import lolcat from Fedora 43 to provide a lightweight component change
for exercising the multi-deployment Control Tower PR-check pipeline.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.

Use the NonOfficial governed template only in the temporary draft PR so
the multi-deployment pipeline can be exercised with its test ADO setup.
This override must not merge into the 4.0 branch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp build

@azure-pipelines

Copy link
Copy Markdown
Command 'build' is not supported by Azure Pipelines.

Supported commands
  • help:
    • Get descriptions, examples and documentation about supported commands
    • Example: help "command_name"
  • list:
    • List all pipelines for this repository using a comment.
    • Example: "list"
  • run:
    • Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
    • Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
  • where:
    • Report back the Azure DevOps orgs that are related to this repository and org
    • Example: "where"

See additional documentation.

@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.

@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.

@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.

Compare AzureCliCredential with the DefaultAzureCredential token used by
the request, while logging only non-secret JWT claims. Also surface safe
APIM and Front Door correlation headers for failed requests.

This diagnostic commit belongs only to the temporary draft test PR and
must not merge into the 4.0 branch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.

Mirror the actual PR's renewable Azure Pipelines WIF credential and
explicit package-build skip fixes in the temporary test environment.
Replace the earlier token diagnostics with the production behavior.

This test-only commit must not merge into the temporary 4.0 base branch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PawelWMS

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant