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

      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
          74 kB
          Dakota Brown
        2. release__not_escaped_logs.JPG
          19 kB
          Dakota Brown
        3. release_escaped_logs.JPG
          24 kB
          Dakota Brown
        4. release_escaped.JPG
          40 kB
          Dakota Brown
        5. release_not_escaped.JPG
          38 kB
          Dakota Brown

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

              Created:
              Updated:
              Resolved: