Json – Groovy with extended choice parameter plugin

boongroovyJenkinsjenkins-pluginsjson

I am trying to cook up a Groovy script to use with the Extended Choice Parameter plugin in Jenkins: https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin.

From the plugin page: the groovy script should return a JSON object that corresponds to the "options" object referred to in https://github.com/jdorn/json-editor. The example script does not work and throws error.

Could someone tell me how I can have Boon.fromJSON() return a JSON editor object? My intention is to have a pre-defined set values beings shown as parameters, each accepting a text against it (i.e, render as textbox).

Example (following the JSON editor way):

{
  "value1": "",
  "value2": "",
  "value3": ""
}

Even if it can be done without using Boon parser, it should be fine.

Best Answer

It's important to note that Boon.fromJSON() takes a String as an argument. The example at the plugin page isn't very clear to someone who may not know groovy very well:

def jsonEditorOptions = Boon.fromJSON(/{
    disable_edit_json: true,
    ...
}/);

The /text/ syntax in groovy is the Slashy String. Disregard this if you are already using this syntax but you haven't provided your code or error received.

Related Solutions

Json – How to POST JSON data with cURL

You need to set your content-type to application/json. But -d (or --data) sends the Content-Type application/x-www-form-urlencoded, which is not accepted on Spring's side.

Looking at the curl man page, I think you can use -H (or --header):

-H "Content-Type: application/json"

Full example:

curl --header "Content-Type: application/json" \
  --request POST \
  --data '{"username":"xyz","password":"xyz"}' \
  http://localhost:3000/api/login

(-H is short for --header, -d for --data)

Note that -request POST is optional if you use -d, as the -d flag implies a POST request.

On Windows, things are slightly different. See the comment thread.

Jenkins – Jacoco coverage in Jenkins Pipeline

The jacoco pipeline step configuration uses this format:

step([$class: 'JacocoPublisher', 
      execPattern: 'target/*.exec',
      classPattern: 'target/classes',
      sourcePattern: 'src/main/java',
      exclusionPattern: 'src/test*'
])

Or with a simpler syntax for declarative pipeline:

jacoco( 
      execPattern: 'target/*.exec',
      classPattern: 'target/classes',
      sourcePattern: 'src/main/java',
      exclusionPattern: 'src/test*'
)

You can find more options in the JaCoCo Pipeline Steps Reference

Best Answer

Related Solutions

Json – How to POST JSON data with cURL

Jenkins – Jacoco coverage in Jenkins Pipeline

Related Topic