This report is created from a single case with an issue - with guess for operation at other common cases.

case 1 - exposes the problem i am seeing:

JOB_NAME=my_job_name/my_git_branch_name
JOB_BASE_NAME=my_git_branch_name

case 2 - similar to case 1:

JOB_NAME=my_job_name/some_git_branch_category_prefix%2Fmy_git_branch_name
JOB_BASE_NAME=some_git_branch_category_prefix%2Fmy_git_branch_name

case 3 - created based upon some small test case:

JOB_NAME=jenkins_job_subfolder_for_testing/my_job_name
JOB_BASE_NAME=my_job_name

case 4 - created based upon some other small test case

JOB_NAME=my_job_name
JOB_BASE_NAME=my_job_name

expectation:

all cases will result in this for the second item - but case 1 and 2 wont do that:

JOB_BASE_NAME=my_job_name

side note - how I did discover that problem:

i found warnings_next_generation/ng plugin having problems with these (at my desk) often lengthy and %-sequences containing branch names. the visualisation was not that usable anymore due to shortening of names (at least in the web display, but maybe at even more places internally) and assume internal malfunctions due to this.