This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: build-pipeline-plugin
    • Environment:
      Jenkins ver. 1.585, Build Pipeline Plugin 1.4.5 + Parameterized Trigger 2.25, Windows Server 2008 R2 Standard, Google Chrome Version 40.0.2214.94 m, Java JDK 1.7.0u25

      With as well as without "Current Build Parameters" in the configuration of job A's manual trigger of job B, job B is passed the build parameters of A's build.

      It should only happen with the "Current Build Parameters" option chosen.

      If job B has environment variables defined with the same name as one of A's parameters, it will be disregarded by e.g. the Gradle plugin, which prefers parameters over environment variables.

        1. view-config.xml
          1 kB
          Sune Keller

            Assignee:
            Unassigned
            Reporter:
            Sune Keller
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: