Skip to content

This repo is used to store build targets for automated builds

Notifications You must be signed in to change notification settings

crdroidandroid/build_targets

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 

Repository files navigation

Repo usage

This repo is used to store build targets for automated builds
Server builds off info stored in crdroid.dependencies

Usage

Add to build_targets based on below info

<device> <build_type> <auto-upload> <saveimages>

Description:

<device> - device codename  
<build_type> - user/userdebug/eng  
<auto-upload> - yes/no (this autouploads complete build and recovery to SF)  
<saveimages> - array of images to save ex. [boot.img, vendor_boot.img]

Dependencies

Each device that's built, needs to have crdroid.dependencies set properly.
Note that you are not allowed to clone via vendor call (git clone).

Format:

[
  {
    "repository": "crdroidandroid/android_device_oem_codename",
    "target_path": "device/oem/codename",
    "branch": "specific branch",
    "remote": "specific from manifest"
  }
]

repository - Mandatory needed to be tracked from crDroid repo for dt (common) and kernel
target_path - Path where to clone repo
branch - Defaults to branch of crdroid remote from default.xml manifest, however can use different one from tracked repo
remote - Defaults to github remote from default.xml manifest, however can use different one from remote list

Note 1: Branch and remote should not be set if using default defined values (ex: with crDroid 10, branch is default to 14.0 while remote is github)
Note 2: As per rules, repos need to be tracked from crDroid GitHub or GitLab for dt, kernel or addons while hardware or some other small dependencies can be tracker from LOS.

About

This repo is used to store build targets for automated builds

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published