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

Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

      Came here through the Build Pipeline plugin issue tracker link. Since the migration from google code, an annoying bug got lost, which I wanted to reinstate here.

      There's a problem when reusing a parameterized downstream project in several upstream projects (with manual run trigger). Only the first upstream project successfully invokes the downstream project retaining parameters set using the groovy script workaround. Other invocations leave the parameters empty in the downstream project.

      Case in point: 30 application projects, 4 environments to deploy to. With this bug we need to duplicate a deploy script per application (per environment). So instead of 4 deploy scripts, we now have 120 deploy scripts.

      This occurs all the way up to the latest version (1.3.3).

      Related issues:
      https://code.google.com/p/build-pipeline-plugin/issues/detail?id=54
      https://code.google.com/p/build-pipeline-plugin/issues/detail?id=53

          [JENKINS-18162] Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

          Benny Bottema created issue -
          Benny Bottema made changes -
          Description Original: Came here through the Build Pipeline plugin issue tracker link. Since the migration from google code, an annoying bug got lost, which I wanted to reinstate here.

          There's a problem when reusing a parameterized downstream project in several upstream projects (with manual run trigger). Only the first upstream project successfully invokes the downstream project retaining parameters set using the groovy script workaround. Other invocations leave the parameters empty in the downstream project.

          Case in point: 30 application projects, 4 environments to deploy to. With this bug we need to duplicate a deploy script per application (per environment). So instead of 4 deploy scripts, we now have 120 deploy scripts.

          Related issues:
          https://code.google.com/p/build-pipeline-plugin/issues/detail?id=54
          https://code.google.com/p/build-pipeline-plugin/issues/detail?id=53
          New: Came here through the Build Pipeline plugin issue tracker link. Since the migration from google code, an annoying bug got lost, which I wanted to reinstate here.

          There's a problem when reusing a parameterized downstream project in several upstream projects (with manual run trigger). Only the first upstream project successfully invokes the downstream project retaining parameters set using the groovy script workaround. Other invocations leave the parameters empty in the downstream project.

          Case in point: 30 application projects, 4 environments to deploy to. With this bug we need to duplicate a deploy script per application (per environment). So instead of 4 deploy scripts, we now have 120 deploy scripts.

          This occurs all the way up to the latest version (1.3.3).

          Related issues:
          https://code.google.com/p/build-pipeline-plugin/issues/detail?id=54
          https://code.google.com/p/build-pipeline-plugin/issues/detail?id=53
          Tom Akehurst made changes -
          Assignee New: Tom Akehurst [ tomakehurst ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          David Fuenmayor made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 149460 ] New: JNJira + In-Review [ 186128 ]
          Andrew Dean made changes -
          Comment [ I'm getting this issue with up to date plugins and it is 2019... I have an upstream job calling a downstream one and it occasionally figures out what to do with parameters but other times it pretends like they don't exist and executes anyway. ]

            tomakehurst Tom Akehurst
            plantface Benny Bottema
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: