# GitHub action for package building and testing

**URL:** <https://forum.openwrt.org/t/github-action-for-package-building-and-testing/91324>\
**Category:** For Developers\
**Created:** [March 16, 2021, 1:29am UTC](https://forum.openwrt.org/t/github-action-for-package-building-and-testing/91324 "2021-03-16T01:29:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aparcar](https://forum.openwrt.org/user_avatar/forum.openwrt.org/aparcar/32/5517_2.png) [@aparcar](https://forum.openwrt.org/u/aparcar)\
**Post date:** [March 16, 2021, 1:29am UTC](https://forum.openwrt.org/t/github-action-for-package-building-and-testing/91324/1 "2021-03-16T01:29:58Z")

</div>

A while ago I wanted to improve the CI for the community package feed and ended up creating a GitHub CI action that uses OpenWrt SDKs to compile packages.

The action is found [here](https://github.com/openwrt/gh-action-sdk/) with a short README explaining how it's used.

The use cases are either compilation testing or compilation of a repository to be offered as a feed:

- [`packages.git`](https://github.com/openwrt/packages/blob/master/.github/workflows/multi-arch-test-build.yml#L63) compiles and runtime tests every Pull Request for popular architectures.
- [LibreMesh](https://github.com/libremesh/lime-packages/blob/master/.github/workflows/build.yml#L19) uses the action to compile their own repository with specialized packages.

Please let me know if you have ideas for improvements.
