CI

[ptheywood]

Basic CI to conifgure and build the template example would be a good addition, and allow users to opt-in to the same (actions shouldn't be enabled when created from a template repo by default iirc)

This would require duplication of the cuda install scripts on CI and increase maintenance burden a little.

[Robadob]

Carpentries org has a gh actions repo, with common actions which other repos inherit. Could this be a relevant way to reduce that duplication?

…

On Fri, 2 Feb 2024 at 12:00, Peter Heywood ***@***.***> wrote: Basic CI to conifgure and build the template example would be a good addition, and allow users to opt-in to the same (actions shouldn't be enabled when created from a template repo by default iirc) This would require duplication of the cuda install scripts on CI and increase maintenance burden a little. — Reply to this email directly, view it on GitHub <#15>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFVGCW5TNOISJNFKEZ4AQLYRTIO3AVCNFSM6AAAAABCWR3S2GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTINZXGYZDCNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ptheywood]

Yes we could potentially do something with re-usable actions in a separate repo. It's been on my list of things to look into.

For 3rd parties, they would have to allow 3rd party re-usable actions, or also fork the actions repo into their org/account.

The other option is turning my very rough install cuda scripts into propper github actions, but I don't have the time nor patience to learn how to do that (it'd been requested on my dev repo for them by others previously, ptheywood/cuda-cmake-github-actions#5).

And that wouldn't work in our manylinux builds either which run in a non gh container)