LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26427 Commits
1 Branch
46 MiB
Tree: 698af2eb99
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '698af2eb99'
${ noResults }
openwrt-packages-dist/.github/workflows/Dockerfile

6 lines
100 B
Raw Normal View History

CI: add runtime tests for packages Additional to manual runtime tests this CI addition runs a custom test script per package. Ideally this lowers the errors of package bumps, something which is time consuming when done manually for multiple architectures. This CI uses the official OpenWrt containers and tries to install and run compiled packages. The run depends on the content of `test.sh`, which is an `ash` script. It's called with the *packge name* and *package version* as arguments. This allows different behaviour if a single package generates multiple IPK files. The version is usable for the most trivial runtime check, e.g. `tmux -V | grep "$2"`. The current approach uses the qus project[1] which contains multiple QEMU binaries to run various architectures. [1]: https://github.com/dbhi/qus Signed-off-by: Paul Spooren <mail@aparcar.org>
4 years ago
CI: use new `openwrt` Docker username We now own `openwrtorg` and `openwrt`, where the latter replaces the former. Slowly migrate over. Signed-off-by: Paul Spooren <mail@aparcar.org>
4 years ago
CI: add runtime tests for packages Additional to manual runtime tests this CI addition runs a custom test script per package. Ideally this lowers the errors of package bumps, something which is time consuming when done manually for multiple architectures. This CI uses the official OpenWrt containers and tries to install and run compiled packages. The run depends on the content of `test.sh`, which is an `ash` script. It's called with the *packge name* and *package version* as arguments. This allows different behaviour if a single package generates multiple IPK files. The version is usable for the most trivial runtime check, e.g. `tmux -V | grep "$2"`. The current approach uses the qus project[1] which contains multiple QEMU binaries to run various architectures. [1]: https://github.com/dbhi/qus Signed-off-by: Paul Spooren <mail@aparcar.org>
4 years ago
​
​
​
 
  1. ARG ARCH=x86-64

  2. FROM openwrt/rootfs:$ARCH

  3. 

  4. ADD entrypoint.sh /entrypoint.sh

  5. 

  6. CMD ["/entrypoint.sh"]