Bonjour, The ceph-backport.sh is used on a regular basis by developers helping with backports: it proved to be stable and robust over the years. Minimal integration tests were added[0] this week to minimize the risk of a regression when improving it, for instance to help with the ordering of backports[1]. The test environment[2] spawns a redmine instance configured in the same way as https://tracker.ceph.com/ and a Gitea instance that has the same API as GitHub[3] with repositories configured in the same way as https://github.com/ceph/ceph/. I think it would make sense to include the tests in the CI[4]. The test itself would do nothing if the PR does not contain any change related to ceph-backport.sh. Does that sound sensible? Cheers [0] https://tracker.ceph.com/issues/51222 [1] https://tracker.ceph.com/issues/51224 [2] https://lab.fedeproxy.eu/ceph/ceph-backport/ [3] https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#api-v1 [4] https://tracker.ceph.com/issues/52122 -- Loïc Dachary, Artisan Logiciel Libre
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
