Skip to content

Conversation

@zanejohnson-azure
Copy link
Contributor

@zanejohnson-azure zanejohnson-azure commented Dec 6, 2025

In brief, this PR adds capability of deploy and test a newly built image by ci build pipeline in dev clusters. At high-level, after an image is built, it will be deployed to dev clusters, which will run testkube to test the new image is working in clusters. The tests performed are what are being used in ci test automation framework.

There are a few TODOs, mostly about replacing/adding more test clusters, and the way to deploy images to clusters. These TODOs have been included and explained as a part of this PR.

The solution supports queuing multiple PRs at the same time, so each PR will be tested one by one in order.

Besides supporting deploy a newly built image from ci build pipeline, it has a few other features:

  • allow user to specify and test any ci image version on ux, then the pipeline will skip build stage and directly test the specified image in the clusters.
  • by default, the test will only run after the PR is merged. However, to allow developers to run test from a branch, dev can include "run-e2e" in its branch name, then the test will run during PR phase as well. This provides flexibility to developers but also prevent from running the tests in all PRs.

Test 1

Common use case that deploys image built by pipeline to test clusters.
https://github-private.visualstudio.com/microsoft/_build/results?buildId=111201&view=results

Test 2

Manually specify image name (i.e. 3.1.33) on pipeline. Pipeline will automatically skip build and just deploys the image to test clusters for testing.
https://github-private.visualstudio.com/microsoft/_build/results?buildId=111213&view=results

@zanejohnson-azure zanejohnson-azure requested a review from a team as a code owner December 6, 2025 19:03
@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@github-actions
Copy link

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions
Copy link

This PR was closed because it has been stalled for 12 days with no activity.

@github-actions
Copy link

This PR was closed because it has been stalled for 12 days with no activity.

@zanejohnson-azure zanejohnson-azure force-pushed the zane/ci-agent-auto-deploy branch from 5f11a32 to 0e1bbb9 Compare January 22, 2026 21:54
@zanejohnson-azure
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

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.

3 participants