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

Splunk Plugin double encoding special characters

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of

      job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>

      So for example:

      job/FOO/job/bar/job/master

      However, when a / exists in the branch name (for example, feature/test), we get something along the lines of

      job/FOO/job/bar/job/feature%2Fbb-test

      Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as

      job/FOO/job/bar/job/feature%252Ftest

      So the % sign seems to be doubly encoded and instead of feature%2Fbb-test we get feature%252Ftest.

      This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

      Other Info:
      Jenkins Version: 2.222.4
      Splunk Plugin Version: 1.9.4
      Jenkins is running in a container on OpenShift

        Attachments

          Activity

          jhoenzsch Josef Hoenzsch created issue -
          jhoenzsch Josef Hoenzsch made changes -
          Field Original Value New Value
          Description I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
          {code:java}
          job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>{code}
          So for example:
          {code:java}
          job/FOO/job/bar/job/master{code}
          However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
          {code:java}
          job/FOO/job/bar/job/feature$2Fbb-test{code}
          Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
          {code:java}
          job/FOO/job/bar/job/feature%252Ftest*{code}

          So the % sign seems to be doubly encoded and instead of feature$2Fbb-test we get feature%252Ftest.

          This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

          Other Info:
          Jenkins Version: 2.222.4
          Splunk Plugin Version: 1.9.4
          Jenkins is running in a container on OpenShift
          I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
          {code:java}
          job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>{code}
          So for example:
          {code:java}
          job/FOO/job/bar/job/master{code}
          However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
          {code:java}
          job/FOO/job/bar/job/feature$2Fbb-test{code}
          Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
          {code:java}
          job/FOO/job/bar/job/feature%252Ftest{code}
          So the % sign seems to be doubly encoded and instead of feature$2Fbb-test we get feature%252Ftest.

          This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

          Other Info:
           Jenkins Version: 2.222.4
           Splunk Plugin Version: 1.9.4
           Jenkins is running in a container on OpenShift
          jhoenzsch Josef Hoenzsch made changes -
          Description I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
          {code:java}
          job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>{code}
          So for example:
          {code:java}
          job/FOO/job/bar/job/master{code}
          However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
          {code:java}
          job/FOO/job/bar/job/feature$2Fbb-test{code}
          Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
          {code:java}
          job/FOO/job/bar/job/feature%252Ftest{code}
          So the % sign seems to be doubly encoded and instead of feature$2Fbb-test we get feature%252Ftest.

          This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

          Other Info:
           Jenkins Version: 2.222.4
           Splunk Plugin Version: 1.9.4
           Jenkins is running in a container on OpenShift
          I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
          {code:java}
          job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>{code}
          So for example:
          {code:java}
          job/FOO/job/bar/job/master{code}
          However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
          {code:java}
          job/FOO/job/bar/job/feature%2Fbb-test{code}
          Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
          {code:java}
          job/FOO/job/bar/job/feature%252Ftest{code}
          So the % sign seems to be doubly encoded and instead of feature$2Fbb-test we get feature%252Ftest.

          This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

          Other Info:
           Jenkins Version: 2.222.4
           Splunk Plugin Version: 1.9.4
           Jenkins is running in a container on OpenShift
          jhoenzsch Josef Hoenzsch made changes -
          Description I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
          {code:java}
          job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>{code}
          So for example:
          {code:java}
          job/FOO/job/bar/job/master{code}
          However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
          {code:java}
          job/FOO/job/bar/job/feature%2Fbb-test{code}
          Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
          {code:java}
          job/FOO/job/bar/job/feature%252Ftest{code}
          So the % sign seems to be doubly encoded and instead of feature$2Fbb-test we get feature%252Ftest.

          This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

          Other Info:
           Jenkins Version: 2.222.4
           Splunk Plugin Version: 1.9.4
           Jenkins is running in a container on OpenShift
          I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
          {code:java}
          job/<BB-PROJECT>/job/<bb-repo>/job/<branch-name>{code}
          So for example:
          {code:java}
          job/FOO/job/bar/job/master{code}
          However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
          {code:java}
          job/FOO/job/bar/job/feature%2Fbb-test{code}
          Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
          {code:java}
          job/FOO/job/bar/job/feature%252Ftest{code}
          So the % sign seems to be doubly encoded and instead of feature%2Fbb-test we get feature%252Ftest.

          This causes a downstream impact where the Splunk App for Jenkins can't find the console logs (despite them existing) for any job where there is a / in the job name.

          Other Info:
           Jenkins Version: 2.222.4
           Splunk Plugin Version: 1.9.4
           Jenkins is running in a container on OpenShift
          fengxx Ted Xiao made changes -
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Fixed but Unreleased [ 10203 ]
          fengxx Ted Xiao made changes -
          Attachment splunk_app_jenkins-1.0.9-0.tar.gz [ 52230 ]

            People

            Assignee:
            fengxx Ted Xiao
            Reporter:
            jhoenzsch Josef Hoenzsch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: