Override PTF_IMAGE_TAG use release tag [202405]#22575
Override PTF_IMAGE_TAG use release tag [202405]#22575bingwang-ms merged 1 commit intosonic-net:202405from
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-pipelines.yml
Outdated
There was a problem hiding this comment.
how about using $(BUILD_BRANCH) and cherry-pick?
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
opcoder0
force-pushed
the
fix-pipeline-202405
branch
from
65975a4 to
1a9b23e
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@opcoder0 Can you address the conflict in 202305 and 202311 branch? Seems the PR test in these two branches is also impacted. |
Hi @bingwang-ms Sure. I have added the approved labels. I am waiting for the PRs to be created so I can fix the conflicts. |
Adding the |
opcoder0
changed the title
…05 (sonic-net#1108) ```<br>* 32312e8 - (HEAD -> 202405) Merge branch '202405' of https://github.com/sonic-net/sonic-buildimage into 202405 (2025-05-10) [Sonic Automation] * 654ae55 - (head/202405) Fix commit - remove submodules (sonic-net#22575) (2025-05-09) [Sai Kiran]<br>```
5 participants
Why I did it
The azure pipeline uses sonic-mgmt master branch to invoke tests. The default value of PTF_IMAGE_TAG on master branch is "latest" which is a Python 3 only image. For release branches we use mixed image which is tagged under branch specific tag name. This PR overrides it here.
Work item tracking
How I did it
Override PTF_IMAGE_TAG in pipeline
How to verify it
TBD
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
NA
Description for the changelog
Override PTF_IMAGE_TAG for release branch PR tests
The azure pipeline uses sonic-mgmt master branch to invoke tests. The default value of PTF_IMAGE_TAG on master branch is "latest" which is a Python 3 only image. For release branches we use mixed image which is tagged under branch specific tag name.
Link to config_db schema for YANG module changes
NA
A picture of a cute animal (not mandatory but encouraged)
NA