On 09.02.21 18:59, Giulio Moro wrote: >> What you are missing is also :opt-xenomai-next.yml because 5.4 requires > > Yes! This worked: > > kas-container build > kas.yml:board-beagle-bone-black.yml:opt-xenomai-next.yml:opt-linux-latest-5.4.yml > > > Then I checked out c6fafd0b83752c529483f7ba3a4277d02ce6aace > (wip/dovetail) and attempted: > > kas-container build > kas.yml:board-beagle-bone-black.yml:opt-xenomai-next.yml:opt-linux-latest-5.10.yml > > > however this failed because `dovetail/master` was not available in > GIT_REPO_armhf. I am submitting a patch separately to fix this. >
Should be fine now, we both fixed it. > I also tried to build with gitlab-runner, but the line provided in the > README didn't work: > > gitlab-runner exec docker --docker-privileged \ > --env "HTTP_PROXY=$HTTP_PROXY" --env "HTTPS_PROXY=$HTTPS_PROXY" \ > --env "NO_PROXY=$NO_PROXY" build:qemu-armhf > > fails with > > FATAL: no job named "build:qemu-armhf" > > Note that I don't have any of those variables set in my env and that I > am not running behind a proxy, but the failure seems to be unrelated (I > am no docker expert), so maybe the README needs update on this one, too? Yeah, our README is totally outdated here. We changed the naming scheme of jobs since then. Plus I'm not sure how to specify the variations (kernel version, Xenomai versions) this way. Quirin? Thanks for reporting in any case. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
