Build Your Own Kernel with Github Action

English | 中文

This Github Action helps you build kernels. It reads multiple kernel sources from a configuration file and builds them using different toolchains. Additionally, it supports patching the kernel with KernelSU and uploading the built kernel image.

---

 
  Configure  
    
  Quick Start  
    
  Local testing  
 

---

• Web page configuration Json compilation configuration file (to be released soon)
• Use MagiskBoot to generate boot.img
• Use script to compile kernel locally
• Webpage for online kernel building
• Support origin / custom AnyKernel3
• Custom build info
• Suppor Docker

This action contains two jobs: Set-repos and Build-Kernel.

The Set-repos job reads the kernel sources from the configuration file and outputs them to the Build-Kernel job. The Build-Kernel job uses the outputted kernel sources to build the kernels and upload the built kernel images.

See repo configuration file guidance.

This project's basic usage is as follows:

1. Fork this project on GitHub.

2. Modify the repos/repos*.json file through the Github website or pull it to your local machine and commit the changes.

3. Go to the Action page on Github and find Build kernels, then Run workflow.

Notice

In this step, you may encounter the following error when executing softprops/action-gh-release@v1:

👩‍🏭 Creating new GitHub release for tag v20230619.7...
⚠️ GitHub release failed with status: 403
undefined
retrying... (2 retries remaining)
👩‍🏭 Creating new GitHub release for tag v20230619.7...
⚠️ GitHub release failed with status: 403
undefined
retrying... (1 retries remaining)
👩‍🏭 Creating new GitHub release for tag v20230619.7...
⚠️ GitHub release failed with status: 403
undefined
retrying... (0 retries remaining)
❌ Too many retries. Aborting...
Error: Too many retries.

The reason for this error is related to workflow permissions:

Complete the permission settings and then you can publish your own Release normally.

4. Wait for the compilation to finish, then download the compiled product from the corresponding page.

5. Use your preferred packaging software to package the kernel (AnyKernel3, Android-Image-Kitchen, MagiskBoot, etc.)

If you don't want to run the action on Github, you can use nektos/act to test this workflow locally and output the files.

This is the recommended local testing process. Simply install nektos/act and run the following command:

# Collect artifacts to /tmp/artifacts folder:
act --artifact-server-path /tmp/artifacts

If you want to store the artifacts in a different location, change /tmp/artifacts to your preferred directory.

If there are errors, use the -v flag to generate an error report and submit an issue. Here's the command:

# Collect artifacts to /tmp/artifacts folder:
act --artifact-server-path /tmp/artifacts -v

If you need to perform a completely local build, consider building as follows:

1. Set up a local Gitea or Gitlab Git service and modify the configuration file address to point to the local service address.

2. Use git daemon to create a secondary image locally.

This is just a suggestion, and we do not provide a specific guide.

• weishu : Developer of KernelSU
• AKR Android Developer Community ： Provides build tutorials
• DogDayAndroid/KSU_Thyme_BuildBot : Predecessor of this project
• xiaoleGun/KernelSU_Action ： Drawing on some Github Actions
• UtsavBalar1231/Drone-scripts ： Drawing on some Github Actions

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.