GitHub Action Script Custom Modded By Eliminater74

Original from P3TERX

Created to make building OpenWRT easier using github actions.

Snapshot changelog: https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog

Notes:

Patches directory are taken from: Divested-WRT: UNOFFICIAL OpenWrt builds
mwlwifi is taken from: Lean's Openwrt source code repository
modifications to action script By Eliminater74
NetData SQM char from: https://github.com/Fail-Safe/netdata-chart-sqm
OpenWRTScripts from: https://github.com/richb-hanover/OpenWrtScripts
autoSQM script from: https://github.com/baguswahyu/autoSQM-damasus.bagus More info here: https://forum.openwrt.org/t/help-to-make-sh-script-for-adjust-sqm-automaticaly/58754
Network interfaces ports status from: https://github.com/tano-systems/luci-app-tn-netports

Latest Release Downloads:

Total Downloads:

Actions-OpenWrt

Repo Updated:

INSTRUCTIONS:

Click the Use this template button from my repo to create your new repo (or fork it)
in the home folder of your linux machine clone the openwrt github repo and yours:

git clone https://github.com/openwrt/openwrt.git
git clone https://github.com/ferboiar/wrt32x.git *change it for your brand new recently created repo

Copy in the new folder "openwrt/" the scripts and the configuration files from your repo:

cp wrt32x/scripts/*.sh openwrt/
mkdir openwrt/patches/
cp -r wrt32x/configs/patches/ openwrt/
cp wrt32x/configs/feeds.conf.default openwrt/
cp wrt32x/configs/wrt32x.config openwrt/

run, from "openwrt/" the commands contained in "manual_generate.sh" script:

./diy-part1.sh
./luci_themes.sh
./DevOpenWRT-Router.sh
./lean_packages.sh
./sirpdboy-package.sh
./scripts/feeds update -a
./scripts/feeds install -a
./scripts/feeds uninstall bluld
cp wrt32x.config .config
git am patches / *. patch
./diy-part2.sh

then make menuconfig, load your .config file and choose the packages you want.
upload your .config file to your repo "/configs" as wrt32x.config
launch "Actions" > "Build OpenWrt Snapshot (TESTING)"> "Run workflow" and choose from your repo:

2 (as wrt32x)
0 (as snapshot)
0 (as snapshot luci feeds location)
0 (as none ngrok / ssh after build)

after 4 or 5h of compilation you will see two new files into "Artifacs":

Flashing process

If you are not sure about your kernel partition size do a sysupgrade from command line Increasing mamba and venom kernel partition to 6MB

Verify compatibility

 - $ fw_printenv | grep "pri_kern_size"; #mamba MUST equal 0x400000
 - $ fw_printenv | grep "priKernSize"; #venom MUST equal 0x0600000

Do not try to change them!

Flashing process: You must always use a factory image when flashing to or away from a resized build.

Create a backup tar
Flash the image via sysupgrade: sysupgrade -F squashfs-factory.img
Restore the backup

Two times, to do the change from both boot partitions. Once, you will be capable of install updates without do this again

TIPS

Note that your repo needs to be public, otherwise you have a strict monthly limit on how many minutes you can use.
Your session can run for up to six hours. Don't forget to close it after finishing your work, otherwise you will continue to occupy this virtual machine, making it impossible for others to use it normally.
Please check the GitHub Actions Terms of Service. According to the TOS the repo that contains these files needs to be the same one where you're developing the project that you're using it for, and specifically that you are using it for the "production, testing, deployment, or publication of [that] software project".

Build OpenWrt using GitHub Actions: Instructions (Use translator)

Advanced

SSH by using ngrok

Click the Settings tab on your own repository, and then click the Secrets button to add the following encrypted environment variables:

NGROK_TOKEN: Sign up on the https://ngrok.com , find this token here.
SSH_PASSWORD: This password you will use when authorizing via SSH.

Send connection info to Telegram

Click the Settings tab on your own repository, and then click the Secrets button to add the following encrypted environment variables:

TELEGRAM_BOT_TOKEN: Get your bot token by talking to @BotFather.
TELEGRAM_CHAT_ID: Get your chat ID by talking to @GetMyID_bot or other similar bots.

You can find Telegram Bot related documents here.