...
https://github.com/project-sunbird/sunbird-core-dataproducts/pull/107
https://github.com/project-sunbird/knowledge-platform/pull/538
https://github.com/Sunbird-Ed/SunbirdEd-portal/pull/5997 (For non docker images)
https://github.com/project-sunbird/sunbird-lmsanalytics-service/pull/69143 (For docker images)
None of the staging automated jenkins files need this change. The staging automated jenkins files are named as auto_build_deploy
...
In terms of adopter use, no functionality has changed. Except we will ship the config files with the default value as
refs/tags/${public_repo_branch}instead ofrefs/heads/${public_repo_branch}since adopters always use tags to build their tag.For Diksha or any other other adopter who usually builds on RC tags, they will use something like this
refs/tags/release-3.7.0_RC1Even just using
release-3.7.0_RC1will work. This will not work only when we have a branch and a tag both with same name. In that case, it would be ambigious and Jenkins can checkout either of them, whichever comes first.