Historically I was caught out by change of use of
branch
vstags
as mentioned by @piero in the thread he linked – I wonder if that changed again and / or the community script has not been updated (??) as illustrated by @jigsaw.
I did a
docker pull registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community
to update the docker image before I started and the changes for the build script in the changed thread are not in the build script in the docker image.
At first sight this part of the error
DEVICE_LIST_V3.0.4-A15: invalid variable name
does not appear to derive from your input.
?
I just tried it again:
[ OmniRom 16 - xtrnaw7@t15g /datapool001/develop/e_a15 ] $ cat build_e_test.sh
docker run \
-e "BRANCH_NAME=v3.0.4-a15" \
-e "CLEAN_BUILD=true" \
-e "DEVICE_LIST=sake" \
-e "DEVICE=ASUS_I006D" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=true" \
-e "WITH_SU=true" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension" \
-e "RELEASE_TYPE=UNOFFICIAL" \
-e "CLEAN_OUTDIR=false" \
-e "CLEAN_AFTER_BUILD=false" \
-e "DELETE_OLD_LOGS=5" \
-e "DELETE_OLD_ZIPS=5" \
-v "/datapool001/develop/e_a15/src:/srv/src" \
-v "/datapool001/develop/e_a15/zips:/srv/zips" \
-v "/datapool001/develop/e_a15/logs:/srv/logs" \
-v "/datapool001/develop/e_a15/tmp:/srv/tmp" \
-v "/datapool001/develop/e_a15/ccache:/srv/ccache" \
-v "/datapool001/develop/e_a15/keys:/srv/keys" \
-v "/datapool001/develop/e_a15/local_manifests:/srv/local_manifests" \
-e "REPO=https://gitlab.e.foundation/e/os/releases.git" \
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community
[ OmniRom 16 - xtrnaw7@t15g /datapool001/develop/e_a15 ] $
[ OmniRom 16 - xtrnaw7@t15g /datapool001/develop/e_a15 ] $ ./build_e_test.sh
Set cache size limit to 50.0 GB
/root/build.sh: line 46: DEVICE_LIST_V3.0.4-A15: invalid variable name
/root/build.sh: line 85: DEVICE_LIST_V3.0.4-A15: invalid variable name
[ OmniRom 16 - xtrnaw7@t15g /datapool001/develop/e_a15 ] $