b9e3fc0964b1be0ada79d41cc4249272e076c640
With the introduction of the custom manifests
update [1], a new bug was found when third-party
packages were added to the project scope. This
new feature was ignoring all custom manifests
that were not part of the official build,
causing errors to happen when such packages
were used
[1] https://review.opendev.org/c/starlingx/root/+/938481
Test Plan:
- PASS: Build package with specific custom manifest
directory (/custom-manifests)
- PASS: Execute build-helm-charts.sh
- PASS: Compare diffs between official and merged manifests
- PASS: Apply generated tarball
- PASS: Execute any commands related to the third-party
package
Closes-Bug: 2095498
Change-Id: Id212e7dd63d7a6013f572a8c217fde6f1b663f9c
Signed-off-by: jbarboza <joaopedro.barbozalioneza@windriver.com>
(cherry picked from commit 3618d3046a)
Description
StarlingX build source tree root
Languages
Python
62.4%
Shell
35.7%
BitBake
1.1%
Dockerfile
0.8%