• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core, (1)
      multijob-plugin
    • MultiJob plugin v1.8, Java v1.6, Jenkins 1.480.3, Red Hat Linux

      1. Create a MultiJob Project
      2. click on it to view it
      3. Click Build Now link

      (nothing happens, no errors)

      The URL of the link is something like

      http://hostname:8080/view/TAB1/view/TAB2/job/My-MultiJob/build?delay=0sec

      If I click on the "Schedule a Build" icon, with a URL like:

      http://hostname:8080/job/My-MultiJob/build?delay=0sec

      it works OK.

      If I go up to the parent View and click on the "Schedule a Build" icon with a URL like:

      http://hostname:8080/view/TAB1/view/TAB2/job/My-MultiJob/build?delay=0sec

      It works OK. (appears to be the same URL that doesn't work from a the first link).

          [JENKINS-16974] Build Now link on MultiJob page doesn't work

          C. S. added a comment -

          Same problem with stopping the job.

          C. S. added a comment - Same problem with stopping the job.

          any solutions yet?
          plugin is fantastic, but cant use it in productive right now cause all the folks in the company complain clicking build now doesnt work

          Philipp Mohrenweiser added a comment - any solutions yet? plugin is fantastic, but cant use it in productive right now cause all the folks in the company complain clicking build now doesnt work

          Same issue here. Please fix.

          Jurgen Van Bouchaute added a comment - Same issue here. Please fix.

          some more details:
          the post request generated is build somehow wrong:
          i get this js exception:

          POST http://myjenkins/job/my-job/undefined 404 (Not Found) prototype.js:1585
          Ajax.Request.Class.create.request prototype.js:1585
          Ajax.Request.Class.create.initialize prototype.js:1550
          (anonymous function) prototype.js:452
          klass prototype.js:101
          build myjenkins:167
          onclick myjenkins:51

          so i assume the uri building is either done wrong by the plugin, or the markup might be wrong, so jenkins's build builder is assuming a wrong element

          Philipp Mohrenweiser added a comment - some more details: the post request generated is build somehow wrong: i get this js exception: POST http://myjenkins/job/my-job/undefined 404 (Not Found) prototype.js:1585 Ajax.Request.Class.create.request prototype.js:1585 Ajax.Request.Class.create.initialize prototype.js:1550 (anonymous function) prototype.js:452 klass prototype.js:101 build myjenkins:167 onclick myjenkins:51 so i assume the uri building is either done wrong by the plugin, or the markup might be wrong, so jenkins's build builder is assuming a wrong element

          David Ishee added a comment -

          If you make the MultiJob a parameterized job, the "build now" link on the right side of the screen no longer works, and the one on the left side of the screen now works.

          The broken vs works icons flip-flop based on whether the job is parameterized or not.

          David Ishee added a comment - If you make the MultiJob a parameterized job, the "build now" link on the right side of the screen no longer works, and the one on the left side of the screen now works. The broken vs works icons flip-flop based on whether the job is parameterized or not.

          David Ishee added a comment -

          If I use the 'b' keystroke, I get this message:

          You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.

          David Ishee added a comment - If I use the 'b' keystroke, I get this message: You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.

          Jesse Glick added a comment -

          Actually a bug in core which just happens to get triggered only by the multijob plugin.

          Jesse Glick added a comment - Actually a bug in core which just happens to get triggered only by the multijob plugin.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly
          core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly
          core/src/main/resources/lib/layout/confirmationLink.jelly
          core/src/main/resources/lib/layout/task.jelly
          http://jenkins-ci.org/commit/jenkins/3c01366e0bc5c3e8de23eb7337e8c3e4dbd7843c
          Log:
          [FIXED JENKINS-16974] Unsafe to define a function in <script> without a generated name, as it could clash with functions defined in unrelated *.jelly that happen to included in the same page.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly core/src/main/resources/lib/layout/confirmationLink.jelly core/src/main/resources/lib/layout/task.jelly http://jenkins-ci.org/commit/jenkins/3c01366e0bc5c3e8de23eb7337e8c3e4dbd7843c Log: [FIXED JENKINS-16974] Unsafe to define a function in <script> without a generated name, as it could clash with functions defined in unrelated *.jelly that happen to included in the same page.

          dogfood added a comment -

          Integrated in jenkins_main_trunk #2595
          [FIXED JENKINS-16974] Unsafe to define a function in <script> without a generated name, as it could clash with functions defined in unrelated *.jelly that happen to included in the same page. (Revision 3c01366e0bc5c3e8de23eb7337e8c3e4dbd7843c)

          Result = SUCCESS
          Jesse Glick : 3c01366e0bc5c3e8de23eb7337e8c3e4dbd7843c
          Files :

          • core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly
          • core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly
          • core/src/main/resources/lib/layout/task.jelly
          • changelog.html
          • core/src/main/resources/lib/layout/confirmationLink.jelly

          dogfood added a comment - Integrated in jenkins_main_trunk #2595 [FIXED JENKINS-16974] Unsafe to define a function in <script> without a generated name, as it could clash with functions defined in unrelated *.jelly that happen to included in the same page. (Revision 3c01366e0bc5c3e8de23eb7337e8c3e4dbd7843c) Result = SUCCESS Jesse Glick : 3c01366e0bc5c3e8de23eb7337e8c3e4dbd7843c Files : core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly core/src/main/resources/hudson/model/AbstractProject/sidepanel.jelly core/src/main/resources/lib/layout/task.jelly changelog.html core/src/main/resources/lib/layout/confirmationLink.jelly

          Code changed in jenkins
          User: Jesse Glick
          Path:
          core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly
          http://jenkins-ci.org/commit/jenkins/b01861a44afa70150f39dff49a3d908c0acb9380
          Log:
          JENKINS-16974 3c01366 was backported as eff76c7 but the merge conflict was incorrectly resolved.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/hudson/views/BuildButtonColumn/column.jelly http://jenkins-ci.org/commit/jenkins/b01861a44afa70150f39dff49a3d908c0acb9380 Log: JENKINS-16974 3c01366 was backported as eff76c7 but the merge conflict was incorrectly resolved.

            jglick Jesse Glick
            idapperdanman David Ishee
            Votes:
            7 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: