Questions about flags in docker building process

[Ph1l]

Hi,
I built an e-0.15-q-20210413-UNOFFICIAL-hotdog.zip with and without signature and the flag that signature Spoofing is restricted. Was wondering which flag composition is the default/best one for the builds. Is there any advice? Am I right that a signature together with restricted spoofing is a good choice?

Another question belongs to OTA_URL. Seems not to be important for unofficial Builds, is it? Was wondering if it makes a difference to leave this flag empty or put the default address into it: “https://ota.ecloud.global/api”.

Here is the command i used for e-0.16-q with restricted spoofing

sudo docker run \
-v “/srv/src:/srv/src:delegated” \
-v “/srv/zips:/srv/zips:delegated” \
-v “/srv/logs:/srv/logs:delegated” \
-v “/srv/ccache:/srv/ccache:delegated” \
-v “/srv/keys:/srv/keys:delegated” \
-e “BRANCH_NAME=v1-q” \
-e “DEVICE_LIST=hotdog” \
-e “SIGN_BUILDS=true” \
-e “SIGNATURE_SPOOFING=restricted” \
-e “OTA_URL=https://ota.ecloud.global/api” \
-e “REPO=https://gitlab.e.foundation/e/os/releases.git” \
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community

The one without spoofing and own signature together with empty OTA:

sudo docker run \
-v “/srv/src:/srv/src:delegated” \
-v “/srv/zips:/srv/zips:delegated” \
-v “/srv/logs:/srv/logs:delegated” \
-v “/srv/ccache:/srv/ccache:delegated” \
-v “/srv/keys:/srv/keys:delegated” \
-e “BRANCH_NAME=v1-q” \
-e “DEVICE_LIST=hotdog” \
-e “OTA_URL=” \
-e “REPO=https://gitlab.e.foundation/e/os/releases.git” \
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community

Thanks in advance for some recommendations. The information in the “HOWTO build /e/” section are very good. Thank you for this, but there are some detailed information missing (maybe because of readability reasons).

Maybe one additional questions: Where should i upload those builds? Is android filehost the best place to upload the builds?

[smu44]

Hi,
OTA URL is irrelevant, as long as you don’t set-up your own OTA server
Ecloud server won’t serve any update for an unofficial build.
So you can delete the line, it will probably be harmless (that’s what I usually do).

AndroidFileHost is a good place … with ad-blocking when using http
You may find difficult to upload your images as server are often overloaded, try others (from France, Germany and Poland are best choices for me).
Downloads are much reliable.

I don’t know about Signature Spoofing …

[petefoth]

@smu44

AndroidFileHost is a good place … with ad-blocking when using http
You may find difficult to upload your images as server are often overloaded, try others (from France, Germany and Poland are best choices for me).

If you are going to be making a few builds, you can request developer status from AFH, and get access to upload via FTP. It is much quicker than the browser-based upload. See this post for more info:

[SOLVED] ROM upload bottleneck

I have found a possible answer on XDA Developers forums Beside account and developer status…one need to request to AFH support for the ftp access and wait till you get your ftp username:password from AFH support At google cloud cd or go to directory where the file you want to upload to AFH curl -ftp-pasv -T ROMNAME.zip ftp://USERNAME:PASSWORD@uploads.androidfilehost.com Login at AFH > File manager > Device > Manage files > Folder > Files > Import ftp > select server (wait till fetch f…

@smu44

I don’t know about Signature Spoofing …

Set it to RESTRICTED, as in the first Docker command. This allows signature spoofing, but only for system apps (i.e. the ones built in to the ROM, and you can trust them )