I work in an OpenStack-related community that uses "Jenkins Job Builder"
to build Jenkins jobs. I don't know a lot about it, but I did manage,
with a lot of help from our infra team, to make the changes required to
build the new project I was adding.
I'm also pretty familiar with Groovy, although I haven't done much with
Groovy in Jenkins besides viewing several presentations on how it works.
I'm really interested in any factual comparisons of JJB with this
"Pipeline as Code" concept in Jenkins 2.0. Seeing some of the other
schisms between the communities I work in, I imagine there aren't too
many people who intimately understand both sides of this, but I'd
appreciate if anyone has any detailed examination of this.
One particular thing that I wonder about, how "testable" or "verifiable"
are scripts using this "new" paradigm, compared to what a production JJB
script would look like? I sometimes hear about JJB scripts that fail at
runtime because there were details that couldn't be verified on the
desktop. Does "Pipeline as Code" deal with this at all?
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/572CDD63.7010104%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
