I make use of the Bitbucket team project plugin for Jenkins and that plugin creates jobs in the format of
So for example:
However, when a / exists in the branch name (for example, feature/test), we get something along the lines of
Now, this is totally fine, as it's just encoding the /, however when it gets sent over to Splunk the source appears as
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.
Jenkins Version: 2.222.4
Splunk Plugin Version: 1.9.4
Jenkins is running in a container on OpenShift