staging/pepe2k/.github, branch v22.03.3

CI: kernel: don't checkout and install feeds

2022-12-07T17:17:55Z

We don't need to checkout feed and install feeds for kernel tests. This saves up to 2 minutes for each target kernel build test. Signed-off-by: Christian Marangi (cherry picked from commit 925e2a155ee4d4cc792fbf68aa9666e32a1f649b)

CI: build: skip sdk adapt to external toolchain on cache hit

2022-12-07T17:17:46Z

On cache hit, skip sdk adapt to external toolchain. This is needed because we cache the already extracted sdk and that is already adapted to be used as external toolchain. Rerunning the adap step will result in the test to fail for missing file as the file are already got wrapped to the external toolchain format. Fixes: 42f0ab028e2e ("CI: build: fix use of sdk as toolchain") Signed-off-by: Christian Marangi (cherry picked from commit 99eaedfe3966b1ca812e8a962197cf91286247f7)

CI: build: fix use of sdk as toolchain

2022-12-06T22:48:07Z

The toolchain included in a sdk have a different format than an external toolchain tar. Since sdk is a more integrated setup doesn't use and include wrapper bin that use the external toolchain config and use an alternative and more standard way to include all the toolchain headers. External toolchain use wrapper.sh to append the configured include header when each tool is called. Fix the sdk toolchain by reverting their own sdk wrapper scripts and to simulate an external toolchain build copying what is done in the toolchain target makefile. This handle compilation error and warning caused by not using fortify header on building packages. Fixes: 006e52545d14 ("CI: build: add support to fallback to sdk for external toolchain") Signed-off-by: Christian Marangi (cherry picked from commit 42f0ab028e2eae0d4e7acf9db7fd68b256f23503)

CI: trigger check also on build and check-kernel-patches workflow change

2022-12-04T20:14:21Z

Since kernel and packages workflow now use a shared build workflow, they also need to react on changes on these shared workflow. Fix this and add these shared workflow to the event paths to check. Signed-off-by: Christian Marangi (cherry picked from commit 644175c29ca11e0a008c58c82986045f738f5c6f)

CI: build: fix matching for openwrt release branch for toolchain parsing

2022-12-04T20:14:21Z

The current match logic doesn't handle test for push events related to stable release (example openwrt-22.03) but only fork with the related prefix (example openwrt-22.03-fixup) Fix wrong matching and while at it also add extra checks to other matching (check if the branch name actually start with the requested prefix) Fixes: e24a1e6f6d7f ("CI: build: add support for external toolchains from stable branch") Signed-off-by: Christian Marangi (cherry picked from commit e3cf2b84e5f8708ca17d931ef60746516c8a2fe4)

CI: fix matching for openwrt release branch for container selection

2022-12-04T20:14:20Z

The current match logic doesn't handle test for push events related to stable release (example openwrt-22.03) but only fork with the related prefix (example openwrt-22.03-fixup) Fix wrong matching and while at it also add extra checks to other matching (check if the branch name actually start with the requested prefix) Fixes: abe8a4824210 ("CI: build: add support for per branch tools container") Signed-off-by: Christian Marangi (cherry picked from commit 65c3d19c4b28ccac0d08d916de0ffa4c0e7b3dc2)

CI: build: add support to fallback to sdk for external toolchain

2022-12-04T16:37:01Z

Add support to use sdk as external toolchain if the packaged external toolchain tar is not found on openwrt servers for build shared workflow. Signed-off-by: Christian Marangi (cherry picked from commit b59ac2a7d0ff427419e86bd38dea3d8910dd7926)

CI: build: add support for external toolchains from stable branch

2022-12-04T16:37:01Z

Add support to use external toolchains from stable branch if we are testing commit targeting stable openwrt branch in kernel and packages workflow. With pr the target branch is parsed and the right toolchain is used. To use the stable toolchain for local testing the branch needs to have the prefix openwrt-[0-9][0-9].[0-9][0-9]- (example openwrt-21.02-fixup) Signed-off-by: Christian Marangi (cherry picked from commit e24a1e6f6d7f08fb766eb11b8008f8fc5b72d072)

CI: build: add support for per branch tools container

2022-12-04T16:37:01Z

Add support in build shared workflow for per branch tools container. With pr the target branch is parsed and the right container is used. To use the stable container for local testing the branch needs to have the prefix openwrt-[0-9][0-9].[0-9][0-9]- (example openwrt-21.02-fixup) Signed-off-by: Christian Marangi (cherry picked from commit abe8a4824210966e0899724bf4561a89216a1e36)

CI: tools: support per branch tools container

2022-12-04T16:37:00Z

Add support to push per branch container tools. For anything not official stick to latest tag that correspond to test run from master. If we are testing something for one of the openwrt stable branch, parse the branch name or the tag and push dedicated tools containers. To use the stable container for local testing the branch needs to have the prefix openwrt-[0-9][0-9].[0-9][0-9] (example openwrt-21.02-fixup) Any branch that will match this pattern openwrt-[0-9][0-9].[0-9][0-9] will refresh the tools container with the matching tag. (example branch openwrt-22.03 -> tools:openwrt-22.03) (example branch openwrt-22.03-test -> tools:openwrt-22.03) Signed-off-by: Christian Marangi (cherry picked from commit 75550771ae76fbcab4160e10b73287f918727384)