Re:Why on earth did we choose Jenkins for 2019?
by itielshwartz on Tuesday December 18, 2018 @12:33PM
(#18708526)
I wrote the "only reasons" as I see them, feel free to correct me.
Also we use scripted pipeline all the way
Re:Why on earth did we choose Jenkins for 2019?
by nuclx on Wednesday December 19, 2018 @04:48AM
(#18714487)
I guess the reasons depend on the environment, in my case a multi-platform embedded product. E.g. in my case I don't have a use for dynamic node instantiation. Testing partly requires fiddling with hardware and diverse system architectures, so these parts have to be done manually. Delivery bundling isn't fully automatable as well, so there isn't a place for Jenkins in the go-to delivery pipeline I have in mind. It would just complicate things imho. So what's left is SCM-based triggering of builds, unittests, dynamic tests (valgrind, sanitizers) and system tests.
The only reasons to still use Jenkins in 2019 are SCM polling and e-mail notification. For manual builds I just use python with fabric for remote builds.