User blog comment:Bielik20/Jenkins RxJs/@comment-11733175-20190821192737/@comment-37517897-20190912074454

Yes, we could have achieved simmilar results by using pipe, you are right. Still there is a lot of parameter mapping (param names, values etc. are not the same across different jobs) and a sheer amount of params data that needs to be provided. Jenkins CLI makes so that you rarely need to type anything. More than that, it hides "less valuable" optional params behind a flag so that user is not overwhelmed by the available options. Last but not least, it just suits our workflow better, we don't need to even open a browser and "additional" work that I have done can be of use to peaple with simmilar demands.

In a pipeline I would still have to write params mapping logic which would have been harded since I am not proficient in groovy. I don't know how easy it would have been to split it into seperate files which would have been necessary to keep the code clean. All in all we are happy with current solution but thank you for your feedback. Cheers :)