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

Multi-branch job has issues triggering downstream multi-branch jobs with a '/' in the name

XMLWordPrintable

      First of all, I'm unsure which component listed needs the change.

      I have some multi-branch jobs to compile GIT branches. One of my repositories contain the code for a jar that needs to trigger downstream jobs when built. So long as the downstream multi-branch job is the development (trunk) branch, it works fine. When I build a "release/*" branch, however, the multi-branch job isn't found. I've attached a few screen shots.

      Please note that the $SUB_JOB_NAME is an injected environment variable. It is populated with the GIT branch name being compiled.

      I tried two different ways.
      1) Escaping the '/' for %2F
      2.) using '/'

      As proof that triggering with the 'development' (trunk) branch works, I attached the log for that. I have also confirmed that my other mulit-branch projects all have a 'release/16.2.0' job

        1. development(trunk)_logs.JPG
          development(trunk)_logs.JPG
          74 kB
        2. release__not_escaped_logs.JPG
          release__not_escaped_logs.JPG
          19 kB
        3. release_escaped_logs.JPG
          release_escaped_logs.JPG
          24 kB
        4. release_escaped.JPG
          release_escaped.JPG
          40 kB
        5. release_not_escaped.JPG
          release_not_escaped.JPG
          38 kB

          [JENKINS-32754] Multi-branch job has issues triggering downstream multi-branch jobs with a '/' in the name

          Dakota Brown added a comment -

          Also, my Tomcat server does have url encoding enabled.

          Dakota Brown added a comment - Also, my Tomcat server does have url encoding enabled.

          Matthew DeTullio added a comment -

          I just tested this with the following environment:

          • Jenkins 1.625.1
          • Parameterized Trigger Plugin 2.31
          • Environment Injector Plugin 1.92.1
          • Multi-Branch Project Plugin 0.5.1
          • Branch API Plugin 1.10
          • Folders Plugin 5.12
          • SCM API Plugin 1.2
          • Git Plugin 2.5.2

          Everything worked even with a slash in the name. I used the EnvInject groovy script return ['SHORT_JOB_NAME': currentJob.name] and freestyle-multi2/${SHORT_JOB_NAME} for the trigger project name.

          Assuming it got fixed somewhere along the line, so closing as can't reproduce

          Matthew DeTullio added a comment - I just tested this with the following environment: Jenkins 1.625.1 Parameterized Trigger Plugin 2.31 Environment Injector Plugin 1.92.1 Multi-Branch Project Plugin 0.5.1 Branch API Plugin 1.10 Folders Plugin 5.12 SCM API Plugin 1.2 Git Plugin 2.5.2 Everything worked even with a slash in the name. I used the EnvInject groovy script return ['SHORT_JOB_NAME': currentJob.name] and freestyle-multi2/${SHORT_JOB_NAME } for the trigger project name. Assuming it got fixed somewhere along the line, so closing as can't reproduce

            mjdetullio Matthew DeTullio
            broda20 Dakota Brown
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: