Alioth moving toward pagure
Alioth moving toward pagure
Posted Jun 16, 2017 21:12 UTC (Fri) by k8to (guest, #15413)In reply to: Alioth moving toward pagure by kfox1111
Parent article: Alioth moving toward pagure
The declarative version of them is extremely under-documented and you can easily find yourself in a situation where you can no longer do what you need using the declarative version of them. Also if you make any sort of syntactical error you get a completely incomprehensible java stack trace where you have to guess what you did wrong.
The imperative version is only fairly under-documented, and while you can almost certainly do what you need, you have to do it using the magic subset of Groovy that happens to work. There's so many undocumented assumptions in how they assume you'll wire your code together, that you spend your time wondering what the next stack trace means for days on end until you get something that works.
Jenkins also is awful independent of jenkinsfiles. In order to get the functionality you want, you'll have to install a number of plugins, and different projects will need different plugins, and they all mutate global logic, breaking each other and Jenkins overall. Unless you want to go through the process of providing a jenkins service per project, you'll be dealing with either the pain of an unreliable service, or the pain of a very hamstrung and degenerate service that doesn't do what the projects need.
If you choose to go down this road anyway because it's "the default", then good luck for you and I hope you don't experience what I deal with every day.
