The "make dtbs" step has been added to the linaro-ci branch, it needs a boolean parameter to be set in the Jenkins build. The name of the parameter has to be "MAKE_DTBS", accepted values are "true" and "false".
I was looking at the Jenkins build:
https://ci.linaro.org/jenkins/view/Linux%20Linaro%20Tracking/job/linux-linaro-tracking-llct-branch_origen-exynos4/configure
and I noted that it is not using trunk versione of linaro-ci (lp:linaro-ci), but instead it is using one branch from Deepti:
bzr branch lp:~deeptik/linaro-ci/llt-config-fragment-changes lci-build-tools
Are there any particular reasons to use that branch?
The "make dtbs" step has been added to the linaro-ci branch, it needs a boolean parameter to be set in the Jenkins build. The name of the parameter has to be "MAKE_DTBS", accepted values are "true" and "false".
I was looking at the Jenkins build:
https:/ /ci.linaro. org/jenkins/ view/Linux% 20Linaro% 20Tracking/ job/linux- linaro- tracking- llct-branch_ origen- exynos4/ configure
and I noted that it is not using trunk versione of linaro-ci (lp:linaro-ci), but instead it is using one branch from Deepti:
bzr branch lp:~deeptik/linaro-ci/llt-config-fragment-changes lci-build-tools
Are there any particular reasons to use that branch?