Patch Set 5: > > osmo-gsm-tester scripts don't use osmo-ci > > So why you've comment in another patch that "each is still callable > on its own" in the context of osmo-gsm-tester and jenkins_* helpers > in osmo-bts? Those are using osmo-ci.
I don't get your question? I hope the reasons why I comment are clear. I can only try to read a real question in this comment. osmo-ci.git is about our "internal" jenkins.osmocom.org setup. You mentioned the osmo-gsm-tester in above comment, after I asked you which users you intend to benefit from this patch; hence I decided to point out that the tester is so far kept separate from osmocom's "internal" jenkins setup on purpose, doesn't use osmo-ci and probably won't ever (it is intended to run on anyone's jenkins, not only ours; installation is easier when those scripts don't need osmo-ci; if we change our jenkins setup, other peoples' jenkins should remain independent, so that we don't need to worry about them in osmo-ci). And true, I want the osmo-ci bts build scripts to still be callable on their own, not necessarily needing the bts_model.sh script, which is an unrelated fact to anything else, and frankly not too much to ask. Anything still unclear? -- To view, visit https://gerrit.osmocom.org/2893 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I840533d5bf9233822bc0534a25c252f1cab0a7b0 Gerrit-PatchSet: 5 Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Owner: Max <msur...@sysmocom.de> Gerrit-Reviewer: Harald Welte <lafo...@gnumonks.org> Gerrit-Reviewer: Max <msur...@sysmocom.de> Gerrit-Reviewer: Neels Hofmeyr <nhofm...@sysmocom.de> Gerrit-Reviewer: neels <nhofm...@sysmocom.de> Gerrit-HasComments: No
