search

libbpf / ci

BPF CI
Other
10 stars 23 forks source link

Remove references to travis-ci/ directory #41

Closed danielocfb closed 1 year ago

danielocfb commented 1 year ago

With https://github.com/libbpf/libbpf/commit/bfdf7653e0c46127bb889a5f73eea803bea1d81a and https://github.com/kernel-patches/vmtest/commit/1656bf12ea2a6b29f3ac5fe274699ef800ab98af we have adjusted both clients of this repository to store their CI related functionality in the ci/ directory, as opposed to travis-ci/. Thus, we can now adjust the references to the latter here as well, and subsequently remove the symbolic links introduced in both repositories as an intermediate solution preventing breakage.

Signed-off-by: Daniel Müller deso@posteo.net

danielocfb commented 1 year ago

Scheduled a CI test run here: https://github.com/kernel-patches/bpf/actions/runs/3200924544

chantra commented 1 year ago

LGTM. You can trigger a CI run by replacing references to libbpf/ci actions to yourrepo@branch like I did in https://github.com/kernel-patches/rcu-rc/pull/12/commits/26140a2452a30044375d263f756c61cd30e77498 so it will validate there is no typo or anything stupid missed.

danielocfb commented 1 year ago

LGTM. You can trigger a CI run by replacing references to libbpf/ci actions to yourrepo@branch like I did in kernel-patches/rcu-rc@26140a2 so it will validate there is no typo or anything stupid missed.

Yep, that's what I did.