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

Build Pipeline plugin fails to inject variables with Manual Trigger

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • build-pipeline-plugin
    • Jenkins 1.651.1
      Build Pipeline Plugin 1.5.2
      Environment Injector Plugin 1.92.1
      Matrix Authorization Strategy Plugin 1.3.2

      When I trigger a build from a Build Pipeline View with a Manual Trigger of a downstream job, there's no variables injection and the job fails.
      If I instead trigger the build as administrator user with the same steps, the downstream job correctly receives all the parameters.
      I also tried to add all the possible permissions with the authorization matrix at job level with no success.

          [JENKINS-35211] Build Pipeline plugin fails to inject variables with Manual Trigger

          Luca Landi created issue -
          Luca Landi made changes -
          Labels New: build-pipeline-plugin
          Luca Landi made changes -
          Description Original: When I trigger a build from a Build Pipeline View with a Manual Trigger of a downstream job there's no variables injection and the job fails.
          If I instead trigger the build as administrator user with the same steps, the downstream job correctly receives all the parameters.
          I also tried to add all the possible permissions with the authorization matrix at job level with no success.           		New: When I trigger a build from a Build Pipeline View with a Manual Trigger of a downstream job, there's no variables injection and the job fails.
          If I instead trigger the build as administrator user with the same steps, the downstream job correctly receives all the parameters.
          I also tried to add all the possible permissions with the authorization matrix at job level with no success.

          Dan Alvizu added a comment -

          This same behavior works for me so something else is going on. Can you provide the config.xml and build.xml of relevant jobs /runs?

          Dan Alvizu added a comment - This same behavior works for me so something else is going on. Can you provide the config.xml and build.xml of relevant jobs /runs?

          Luca Landi added a comment -

          Hi dalvizu I just solved today the issue.
          The specific user that is supposed to trigger the job from the pipeline should have the same permissions across upstream and downstream jobs.
          In my specific case the upstream job was without the authorization matrix (and then without authorization for the specific user); granting the same permissions as the downstream job, enabled the injection of the parameters from the job.

          Luca Landi added a comment - Hi dalvizu I just solved today the issue. The specific user that is supposed to trigger the job from the pipeline should have the same permissions across upstream and downstream jobs. In my specific case the upstream job was without the authorization matrix (and then without authorization for the specific user); granting the same permissions as the downstream job, enabled the injection of the parameters from the job.

          Luca Landi added a comment -

          Closing the ticket.

          Luca Landi added a comment - Closing the ticket.
          Luca Landi made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 171439 ] New: JNJira + In-Review [ 210095 ]

            Unassigned Unassigned
            landil Luca Landi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: