Key English
build-e.md:100 The device code can be found on [/e/ devices list](../devices), [LineageOS wiki](https://wiki.lineageos.org/devices/) or with the following command: `$ adb shell getprop ro.product.device`
build-e.md:102 {% include alerts/tip.html content="We now use git tags in addition to a specific manifest for each release. It let us to know exactly what's inside each build." %}
build-e.md:106 > If you want to build a test version, you can use:
> - `BRANCH_NAME` set to v1-nougat, v1-oreo , v1-pie or v1-q to get the last test build
> - `BRANCH_NAME` set to v1-nougat, v1-oreo , v1-pie or v1-q & `REPO=https://gitlab.e.foundation/e/os/android.git`
build-e.md:108 ---
build-e.md:110 To understand what these parameters mean, check the document given [here](docker-command-details)
build-e.md:123 Example for Samsung Galaxy S9
```shell
$ sudo docker run \
-v "/srv/e/src:/srv/src" \
-v "/srv/e/zips:/srv/zips" \
-v "/srv/e/logs:/srv/logs" \
-v "/srv/e/ccache:/srv/ccache" \
-e "BRANCH_NAME=v0.9-pie" \
-e "DEVICE_LIST=starlte" \
-e "REPO=https://gitlab.e.foundation/e/os/releases.git" \
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community
```
build-e.md:125 ### 5. Build options
build-e.md:127 You can now customize applications installed by default in /e/OS.
build-e.md:130 * if you want to add extra applications to the default applications: add your APK to the android_prebuilts_prebuiltapks/ directory, and set the `CUSTOM_APPS` environment variable accordingly in the Docker image, before building.
* if you want to keep a minimal /e/OS build, set the `MINIMAL_APPS` environement variable to true (default is false). For now it's removing LibreOffice viewer, PDFViewer, Maps and Weather.
build-e.md:132 ### 6. Get your image!
build-e.md:134 When your build is finished, please find your images inside `/srv/e/zips/<my-device>` folder. To install, please refer to our [documentation](../../devices).
build-e.md:138 ## Need more help
build-e.md:140 If you need help, please join us on our [community support Telegram channel](https://t.me/joinchat/Fzzi3kUbP-AcoQz3zYHl5A) or get help from other users [on our forum](https://community.e.foundation/c/e-devices/unofficial-builds/92) who build /e/ unofficial ROM's
build-e.md:142 To find more information about our docker image and its environment variables [here](https://gitlab.e.foundation/e/os/docker-lineage-cicd).
build-e.md:143 To report an issue about a build, please refer to [issues documentation](report-an-issue)
build-e.md:16 * The source code has been modified and if the ROM is redistributed, we have several requirements:
* Any reference to /e/, including “/e/”, and our logo must be removed from the build
* The redistribution must not let people think that it is /e/.
* **The ROM name must be changed** and possibly say that it’s been forked from /e/
* Calls to our OTA server infrastructure should be removed
* Custom ROMs can be built on /e/ servers only for exceptional reasons (special development…).
build-e.md:2 ## /e/OS Build Types
build-e.md:22 ### Unofficial /e/ builds
* Source code can be modified only to reach full support on the target device.
* /e/ features, list of installed apps etc. shouldn’t be modified
* Unofficial builds can be published on the /e/ website at a specific place with warnings and a list of what works/what doesn’t work
* It doesn’t have nightly builds nor OTA updates.
build-e.md:28 ### Community builds
* The level of quality is considered high, security updates are applied if possible,
* There may or may not be a ROM maintainer
* Community builds have nightly builds and can be updated OTA
* Source code have to be hosted on our GitLab instance, or on trusted sources (LineageOS GitHub group, AOSP).
build-e.md:34 ### Official /e/ builds
* The level of quality must have reached our conditions.
* It must have an official maintainer.
* Official builds have nightly builds and can be updated OTA.
* Source code have to be hosted on our GitLab instance, or on trusted sources (LineageOS GitHub group, AOSP).