News for hackers. Stuff that matters.
Re:Untangling Jenkins by oblio on Monday December 25, 2017 @04:54PM (#16005885)
There's a Declarative Pipeline these days plus you can turn on the Groovy sandbox. There's also a YAML based thing but I forgot its name.
Re:Untangling Jenkins by grogenaut on Monday December 25, 2017 @06:05PM (#16006124)
Can you provide links? I'm on a plane so very hard to Google.

Seriously? Downvotes? On a holiday on a plane and I get down votes asking for a little help? I did try and google and didn't find the stuff.

Re:Untangling Jenkins by jeremya on Monday December 25, 2017 @10:22PM (#16006877)
I agree it's not easy to Google for the Declarative Pipeline or Groovy Sandbox. Here's the comparison of the two syntaxes available in Jenkins Pipeline (Scripted and Declarative):

https://jenkins.io/doc/book/pipeline/syntax/#compare

Here are details on the Groovy Sandbox (provided by the Script Security Plugin and installed by default when installing recent Jenkins). The Groovy Sandbox is on by default for Jenkins Pipeline:

https://jenkins.io/doc/book/managing/script-approval/

Re:Untangling Jenkins by grogenaut on Tuesday December 26, 2017 @02:21AM (#16007589)
thanks
Re:Untangling Jenkins by RyJones on Monday December 25, 2017 @11:33PM (#16007087)
We use JJB, which is YAML based.

https://github.com/hyperledger/ci-management/tree/master/jjb

for instance

Re:Untangling Jenkins by grogenaut on Tuesday December 26, 2017 @02:21AM (#16007591)
thanks
Re:Untangling Jenkins by jnsaff2 on Tuesday December 26, 2017 @01:55AM (#16007537)
Yea but the declarative pipelines have cheat codes that allow cheeky (read lazy) people to still run code in the pipeline:(