Install sonic yangs during pipeline build #124
Conversation
sachinholla
force-pushed
the
azp_sonicyang
branch
from
11d9dd6 to
b176ee4
Compare
* Download & install sonic_yang_models.whl before build * Download source code and artifacts for the build branch only * Download from pipeline 142, which runs on all branches
sachinholla
force-pushed
the
azp_sonicyang
branch
from
b176ee4 to
1b691ea
Compare
| patterns: | | ||
| target/debs/buster/libyang*.deb | ||
| target/python-wheels/bullseye/sonic_yang_models*.whl |
There was a problem hiding this comment.
Can you learn a Debian distribution on the fly instead?
There was a problem hiding this comment.
Do you have any references? I could not find another such instance.
Not sure how to determine it generically. Did not find any settings in debian/control or any other setting files under sonic-mgmt-framework repo. As per my understanding the target debian version is chosen buy the docker build rules file, by adding the docker image file name to different makefile variables -- like here and here. These docker makefiles are not used during pipeline builds. In fact we do not download sonic-buildimage code as well. Even if we donwload we cannot invoke these makefiles directly. Also, the code pattern is not generic enough to grep & determine the debian version.
Why I did it
Translib now consumes select sonic yangs from
sonic-yang-models.whlduring compile time as well as runtime. Hence pipeline builds needs to install the appropriatesonic_yang_models.whlfor all translib functionalities to be available for testing.Also, the pipeline is always downloading sonic-mgmt-common code and other artifacts from master branch. This may not work if we run the pipeline build on other branches. Pipeline should use artifacts of build branch only.
How I did it
How to verify it
PR build