How to update a local repository for /e/ 2.9-t to 3.0-t?

[bnsmb]

What is the correct process to update the local repository for building /e/ in a Docker image from one version to another version (e.g. from 2.9-t to 3.0-t)?

[piero]

repo sync

Is the command to update to latest branch v1-t

[bnsmb]

well, “repo sync” is used for other AOSP distributions.

But /e/ uses a docker image for building the OS image . I tried this command

docker run \
    -e "BRANCH_NAME=v3.0-t" \
    -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 "/devpool001/develop/e/src:/srv/src" \
    -v "/devpool001/develop/e/zips:/srv/zips" \
    -v "/devpool001/develop/e/logs:/srv/logs" \
    -v "/devpool001/develop/e/tmp:/srv/tmp" \
    -v "/devpool001/develop/e/ccache:/srv/ccache" \
    -v "/devpool001/develop/e/keys:/srv/keys" \
    -v "/devpool001/develop/e/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

to update an existing repository tree with source files for v2.9-t but the build failed.

I don’t remember the exact error message - I tested this some time ago. In the end I gave up and created a new repository tree with the command shown above. But that should not be the correct update process I guessBut that shouldn’t be the correct update process, I think.

[aibd]

@bnsmb

the correct process to update the local repository for building /e/ in a Docker image

You could consult Files · master · e / os / docker-lineage-cicd · GitLab and the dockerfile but it should be automatic. repo sync is included in the build script, build-community.sh

For instance if you specify the branch as v1-t every docker run will upgrade to the point specified here Tags · e / os / 🚀 Releases · GitLab.

Edit. Did you get docker to build a simple supported device before moving on to a Custom build?

[bnsmb]

Did you get docker to build a simple supported device before moving on to a Custom build?

I have successfully built a working OS image for the ASUS Zenfone 8 using the docker image