Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Debugging Pipelines/Groovy is horrible. The stacktraces are horrible. You don't even get a line number for the error!

Also, the documentation badly needs updates and examples.

(Also, amusingly, we chatted a bit by mail on April 25th 2018, but there was no follow up on your side, I guess priorities changed...)



You can use the YAML-like declarative syntax [1] instead to configure the pipelines for 90% of what you do, and just use Apache Groovy for the more complex logic, or interfacing with plugins.

[1] https://jenkins.io/doc/book/pipeline/syntax/


I am using the declarative syntax. It's just as horrible to debug. Play around with it a bit, delete some characters, misconfigure it. You won't even get a line number, just as I said.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: