Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36485

Create/Update of job via API does not keep entity encoding

XMLWordPrintable

      In Jenkins 2.11, after uploading a Job, the entities at least in textareas are no longer encoded
      Steps to verify:

      1) Create a job with e.g. shell code in a build step and some encoded characters (e.g. quotation marks: ")
      2) Download the job config via the REST-API
      -> quotes are encoded as """
      3) re-upload/Replace the same job/data again
      4) Download the configuration again & compare with result of step 2)
      -> quotes are not encoded
      Optional step:
      5) Save the job again via the GUI by clicking SAVE
      6) Download the cofiguration via the API again and compare with result of step 2)
      -> Both download are identical, i.e. the quotes are encoded again

      With an account on the server and wireshark we could verify that the configuration is sent/uploaded correctly (=encoded) to the server in step 3), but stored unencoded on the serversin the local XML. This is corrected after savig again in step 5)

          [JENKINS-36485] Create/Update of job via API does not keep entity encoding

          Frank Yehat added a comment -

          It works as expected (i.e., always encoded) in an older Jenkins installation (1.6xx)

          Frank Yehat added a comment - It works as expected (i.e., always encoded) in an older Jenkins installation (1.6xx)

            Unassigned Unassigned
            pkunk Frank Yehat
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: