ci: build package for Turris

Thanks for all the help, @jpavlinec !

I placed the packaging files into distro/turris. If there are any updates to them, please don't hesitate to open a merge request :)

The only concern I have is we can only do builds from this public repo with the current setup. Would it be possible to convince the openwrt Makefile to use a specific directory, or a tarball instead of providing COMMIT_SHA, which is then downloaded from upstream?

I think that both variants are possible (building from the local directory and/or from a tarball.

Local version requires changes similar to https://github.com/mwarning/openwrt-examples/blob/master/example3/Makefile#L30

And tarball version is used in our repo https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/test/net/knot-resolver/Makefile#L16

I can see the only downside of that solution that you can list what version of the package you have installed right now. And It can be useful to know commit hash.

Full name of the package is built from variables PKG_NAME-PKG_VERSION-PKG_RELEASE (which are defined inside Makefile).

On router:

root@turris:/# opkg list|grep knot-resolver
knot-resolver - 3.1.0-1.2

added 2 commits

• 0f28bf41 - fixup! distro/turris: import packaging files
• cdf724b7 - fixup! gitlabci: run Turris build in CI

Compare with previous version

marked as a Work In Progress from 0f28bf41

added 1 commit

• ebab3500 - fixup! gitlabci: run Turris build in CI

Compare with previous version

added 1 commit

• afc7bac2 - fixup! gitlabci: run Turris build in CI

Compare with previous version

added 1 commit

• 501e8857 - fixup! gitlabci: run Turris build in CI

Compare with previous version

I wonder – do you have any plans on how we'll "synchronize" the distro/turris/ here with the same in https://gitlab.labs.nic.cz/turris/turris-os-packages ?

added 2 commits

• a3b28ed3 - WIP: debug archive
• d65e058c - scripts/make-archive.sh: make script verbose

Compare with previous version

@vcunat We discussed this topic with @tkrizek , and easiest solution will be that I'll send MR with changes from turris-os-packages.

OK, I suppose we'll copy and MR both ways, and we'll see how it works out. Using git submodule would probably be too much hassle for this.

added 3 commits

• 3b0917ec - ci/turris: add Docker container for Turris builds
• 7a27448f - distro/turris: import packaging files
• e1100205 - gitlabci: run Turris build in CI

Compare with previous version

unmarked as a Work In Progress

changed the description

@jpavlinec Thanks for the examples, I've updated the build scripts to use our tarballs. The development versions also contain the git commit, so version numbers should be fine.

The manual sync of packaging files isn't optimal, but we have to do it for other distros as well anyway.

Right, I didn't realize. It's good to keep this more uniform among the different distros.

Any issues / comments? I think it's good to merge as it is now.

I considered my expectation that it will delay the startup of the test stage in all our CI runs by roughly a minute, but that doesn't seem a big deal and we can easily move the job later anyway. EDIT: now a new run was quick, so perhaps it was just bad luck before.

added 39 commits

• e1100205...1aabd4a9 - 36 commits from branch master
• 766a9e65 - ci/turris: add Docker container for Turris builds
• 761a1069 - distro/turris: import packaging files
• 6013c8be - gitlabci: run Turris build in CI

Compare with previous version

enabled an automatic merge when the pipeline for 6013c8be succeeds