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

Promotion does not work if job name contains a whitespace

      I have two jobs:

      • "Job Upstream" is using an SCM trigger and builds several artefacts
      • "Job Downstream" is running hourly and uses artefacts from "Job Upstream" to execute tests. "Job Downstream" is used as a promotion criteria for "Job Upstream". E.g. if "Job Downstream" is successful, then "Job Upstream" is promoted.

      As there is no direct upstream/downstream relationship, I rely on the artefacts fingerprints to establish the relationship between a build from "Job Downstream" and its build source from "Job Upstream". Recording of fingerprints is enabled on both jobs. I can see that fingerprints are correctly recorded and this shows that an artefact from a build from "Job Upstream" has been used by a build from "Job Downstream".

      Expected result: Once a build from "Job Downstream" is successful, the corresponding build from "Job Upstream" should be promoted.

      Actual result: Promotion does not happen and I have the following error message in the console of the build from "Job Downstream":

       WARNING: Job Upstream appears to use this job as a promotion criteria, but no fingerprint is recorded. Fingerprint needs to be enabled on both this job and Job Upstream. See http://hudson.gotdns.com/wiki/display/HUDSON/Fingerprint for more details

      If I rename "Job Upstream" to "JobUpstream" (e.g. remove the whitespace in the middle), then promotion works as expected and a successful build from "Job Downstream" actually triggers the promotion of the associated build from "JobUpstream"

      The whitespace in "Job Downstream" does not seem to have an influence on this issue.

      Affects versions:

      • Jenkins 1.554.1
      • promoted build plugin: 2.17

          [JENKINS-23060] Promotion does not work if job name contains a whitespace

          Mike Corum added a comment -

          How do we increase the priority on this 5-year old issue?  This is a pretty serious issue if people have naming conventions for jobs.  This is still happening with Jenkins v2.173 and promoted build plugin version 3.2.

          Mike Corum added a comment - How do we increase the priority on this 5-year old issue?  This is a pretty serious issue if people have naming conventions for jobs.  This is still happening with Jenkins v2.173 and promoted build plugin version 3.2.

            Unassigned Unassigned
            gregorylenoble Gregory Lenoble
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: