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

Triggering Manual Steps doesn't work in combination with cloudbees-folder

XMLWordPrintable

      We already had a Build Pipeline overview of existing jobs with downstream triggers.

      Afterwards, the Folder plugin was installed and all relevant jobs were moved to the newly created folder.

      Jobs which use the normal Trigger Parametrized build on other project work, but then it's broken for jobs using the Build Other Project (Manual Step).

      When looking at the Build Pipeline view, triggering the Manual Job results in a progressbar running, but then turns back to the state of a job which hasn't been run before (at this point a stack trace with exceptions is being thrown)

        1. Trace.txt
          24 kB

          [JENKINS-28867] Triggering Manual Steps doesn't work in combination with cloudbees-folder

          Christian Karlsson added a comment -

          Front end error:

          POST http://server:8080/$stapler/bound/f80b9adc-fee6-43a3-a6e4-069d87dea705/triggerManualBuild 500 (Server Error)
Ajax.Request.Class.create.request	@	prototype.js:1585
Ajax.Request.Class.create.initialize	@	prototype.js:1550
Object.extend.__method	@	prototype.js:452
klass	@	prototype.js:101
proxy.(anonymous function)	@	bind.js:51
BuildPipeline.triggerBuild	@	build-pipeline.js:80
onclick	@	(index):126

          Christian Karlsson added a comment - Front end error: POST http: //server:8080/$stapler/bound/f80b9adc-fee6-43a3-a6e4-069d87dea705/triggerManualBuild 500 (Server Error) Ajax.Request. Class .create.request @ prototype.js:1585 Ajax.Request. Class .create.initialize @ prototype.js:1550 Object .extend.__method @ prototype.js:452 klass @ prototype.js:101 proxy.(anonymous function) @ bind.js:51 BuildPipeline.triggerBuild @ build-pipeline.js:80 onclick @ (index):126

          Christian Karlsson added a comment -

          I just figured out a workaround.
          In the Downstream Project Names field, you enter the full path to the downstream job.
          Example:
          You have your folder: Organisation >> Projects >> Customer_service
          with jobs build, deployTest.
          Now the Downstream Project Names field need to specify Organisation/Projects/Customer_service/deployTest.

          Christian Karlsson added a comment - I just figured out a workaround. In the Downstream Project Names field, you enter the full path to the downstream job. Example: You have your folder: Organisation >> Projects >> Customer_service with jobs build , deployTest . Now the Downstream Project Names field need to specify Organisation/Projects/Customer_service/deployTest .

          Daniel Serodio added a comment -

          The workaround suggested by kassen does work, even thou the Organization/ prefix looks like a relative path (since it does not start with a /) but is in fact absolute.

          Daniel Serodio added a comment - The workaround suggested by kassen does work, even thou the Organization/ prefix looks like a relative path (since it does not start with a / ) but is in fact absolute.

          Daniel Serodio added a comment -

          Closing as duplicate of JENKINS-23532 since that one is older and has more information than this one.

          Daniel Serodio added a comment - Closing as duplicate of JENKINS-23532 since that one is older and has more information than this one.

            Unassigned Unassigned
            carroarmato0 Christophe Vanlancker
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: