looking at e / os / android · GitLab i understand new convention for BRANCH_NAME is now simply a14 and no more v1-u or v1-a14
look like “v” is now only use for tags
After starting multiple builds (I am trying to build with an unofficial manifest for LineageOS, so I don’t expect help for my specific use case)
with the repo way and the docker way, I don’t know what to do.
repo init, sync, …, brunch start, but ninja is terminated because it uses 100% cpu and I can’t find how to set a limit.
The manifest I got requires LineageOS 21, except “t” seems to be with LineageOS 20 only. And “a14” or “a15” won’t work because of the issue mentioned above.
I haven’t found a bugtracker, I am 99% sure it is a bug with the new branch naming containing numbers (check first message).
I ran docker with an additional -v "/srv/e/local_manifests:/srv/local_manifests" -v "/srv/e/build-community.sh:/root/build.sh" to override build-community.sh, and it was able to start the build with v3.0.4-a14.
diff build-community.sh
diff --git a/build-community.sh b/build-community2.sh
index 5d3c5e6..bf7d217 100644
--- a/build-community.sh
+++ b/build-community2.sh
@@ -41,7 +41,7 @@ fi
# Treat DEVICE_LIST as DEVICE_LIST_<first_branch>
first_branch=$(cut -d ',' -f 1 <<<"$BRANCH_NAME")
if [ -n "$DEVICE_LIST" ]; then
- device_list_first_branch="DEVICE_LIST_$(sed 's/.*-\([a-zA-Z]*\)$/\1/' <<<$first_branch)"
+ device_list_first_branch="DEVICE_LIST_$(sed 's/.*-\([a-zA-Z0-9]*\)$/\1/' <<<$first_branch)"
device_list_first_branch=${device_list_first_branch^^}
read $device_list_first_branch <<<"$DEVICE_LIST,${!device_list_first_branch}"
fi
@@ -80,7 +80,7 @@ if [ "$LOCAL_MIRROR" = true ]; then
fi
for branch in ${BRANCH_NAME//,/ }; do
- branch_dir=$(sed 's/.*-\([a-zA-Z]*\)$/\1/' <<<$branch)
+ branch_dir=$(sed 's/.*-\([a-zA-Z0-9]*\)$/\1/' <<<$branch)
branch_dir=${branch_dir^^}
device_list_cur_branch="DEVICE_LIST_$branch_dir"
devices=${!device_list_cur_branch}