Added pipeline along with auto fetch of build ids and publishing the result to Dashboard! #98
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bfjelds
reviewed
Aug 11, 2025
| - key: ob_outputDirectory | ||
| value: $(Build.ArtifactStagingDirectory)/e2e | ||
| steps: | ||
| - template: e2e-template.yml |
There was a problem hiding this comment.
e2e template is its own stage, you can't call it from steps or jobs. also, please call trident-platform-cicd-template.yml rather than e2e template.
see trident-cicd for how: https://github.com/microsoft/trident/blob/user/bfjelds/enable-idc-testing-artifact/.pipelines/trident-cicd.yml for how
bfjelds
reviewed
Aug 11, 2025
| @@ -0,0 +1,51 @@ | |||
| # .pipelines/trident-pr-e2e-auto.yml | |||
There was a problem hiding this comment.
this should be called something like trident-cicd-for-azl, it isn't a pr-e2e test.
bfjelds
reviewed
Aug 11, 2025
| displayName: "Resolve run IDs (tag: ${{ parameters.baseImgTag }})" | ||
| env: | ||
| SYSTEM_ACCESSTOKEN: $(System.AccessToken) | ||
|
|
There was a problem hiding this comment.
stage 1 should call this to create an artifact with the build ids:
- template: stages/base_image_config/create-base-image-config-artifact.yml
parameters:
baseimgBuildType: dev
baseImagePipelineBuildId: $(ResolvedBaseImagePipelineBuildId)
baseImageArm64PipelineBuildId: $(ResolvedBaseImageArm64PipelineBuildId)
bfjelds
reviewed
Aug 11, 2025
| AUTH="Authorization: Bearer $(System.AccessToken)" | ||
| ACCEPT="Accept: application/json; api-version=7.1-preview.7" | ||
|
|
||
| fetch_latest_with_tag () { |
There was a problem hiding this comment.
does this code make sure that these builds are related to eachother? it seems like it is just finding the most recent.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔍 Description
Added pipeline along with auto fetch of build ids and publishing the result to Dashboard!
Why is this PR needed?
This PR will address following.
1- A new pipeline which will pull build ID of ARM/AMD prod image run and call the trident run.
2- Trident test runs will publish the artifact
3- New pipeline will download junit test result and call template to upload to test result DB dashboard.
4- Also provide a feature to toggle bare metal test.