In view of https://github.com/coq/coq/pull/15027 I am wondering @Gaëtan Gilbert if we should provide a bit more structure to the CI scripts; the implementation there doesn't seem scalable to me.
Maybe we have reached the point bash is not the right tool for us anymore?
it works ok so far, but if you want to do that work don't let me stop you
well that last PR has me unconvinced, seems quite fragile to have to ensure every script includes the boilerplate
It doesn't worry me because people usually copy existing boilerplate to add new CI targets.
That being said, if you want to convert this stuff to a new language, feel free to do it.
One problem though is that if you choose to use a language that we don't already know well (e.g. Ruby) then we'll need to learn that to help maintain it.
Not that I know shell so well either :stuck_out_tongue_closed_eyes:
Doing that in bash would also be fine, we can make the scripts to export
build() and call them from the CI script, if we top driver needs some then store the funcs in an array
I'm not sure using another language will make the scripts any easier to maintain. But I agree that structuring/documenting them a bit more is a good step forward.
Last updated: Sep 30 2023 at 15:01 UTC