• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • git-plugin
    • None

      We discoverd that parameters of one Pipeline job affect the parameters of other jobs. This means that in a job you have multiple parameters with the same name. A part of the parameters is from the current job the rest is defined in another (independent) job. (Both jobs should run simultaneously (but independent from each other) on the same Repository/PullRequest)

      Is this normal? Can I configure that parameters are only valid for one specific Job.

      Example: Two jobs have the Parameter "BranchSpecifier". The Parameter in Job A is set to "develop" and in Job B to "master". What is happening is that both Jobs now have two times the Parameter "BranchSpecifier" – once with value 'develop' and once 'master'.
      --> This is valid for all Parameters of both jobs (in both directions)

       

      Note: Job B in this example was created by copying Job A.
      Also the mentioned parameter in the example is used in the Job config as specifier for the branch the job will use to check out the Pipeline scripts from our Pipeline repo. This way we can trigger the job using pipeline scripts  from another branch (for tests).

      The effect of this bug is that both jobs will check out  the same branch and nt the one specified in the parameter.

          [JENKINS-45472] Job parameters appear in multiple jobs

          Christian Ditscher created issue -
          Christian Ditscher made changes -
          Description Original: We discoverd that parameters of one Pipeline job affect the parameters of other jobs. This means that in a job you have multiple parameters with the same name. A part of the parameters is from the current job the rest is defined in annother (independent) job.


           Is this normal? Can I configure that parameters are only valid for one specific Job.

          Example: Two jobs have the Parameter "BranchSpecifier". The Parameter in Job A is set to "develop" and in Job B to "master". What is happening is that both Jobs now have two times the Parameter "BranchSpecifier" – once with value 'develop' and once 'master'.
          --> This is valid for all Parameters of both jobs (in both directions)

           

          Note: Job B in this example was created by copying Job A.
          Also the mentioned parameter in the example is used in the Job config as specifier for the branch the job will use to check out the Pipeline scripts from our Pipeline repo. This way we can trigger the job using pipeline scripts  from another branch (for tests).

          The effect of this bug is that both jobs will check out  the same branch and nt the one specified in the parameter.
          New: We discoverd that parameters of one Pipeline job affect the parameters of other jobs. This means that in a job you have multiple parameters with the same name. A part of the parameters is from the current job the rest is defined in another (independent) job. (Both jobs should run simultaneously (but independent from each other) on the same Repository/PullRequest)

          Is this normal? Can I configure that parameters are only valid for one specific Job.

          Example: Two jobs have the Parameter "BranchSpecifier". The Parameter in Job A is set to "develop" and in Job B to "master". What is happening is that both Jobs now have two times the Parameter "BranchSpecifier" – once with value 'develop' and once 'master'.
           --> This is valid for all Parameters of both jobs (in both directions)

           

          Note: Job B in this example was created by copying Job A.
           Also the mentioned parameter in the example is used in the Job config as specifier for the branch the job will use to check out the Pipeline scripts from our Pipeline repo. This way we can trigger the job using pipeline scripts  from another branch (for tests).

          The effect of this bug is that both jobs will check out  the same branch and nt the one specified in the parameter.
          Christian Ditscher made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]

          uday reddy added a comment -

          you can use parameterized trigger plugin will work for type of scenarios

          uday reddy added a comment - you can use parameterized trigger plugin will work for type of scenarios

          Hi uday reddy,

          may I get some more info of how to use the parametrized trigger plugin?

          What we want is to trigger several pipelines from one pull request. All of them shall return the build result to BitBucket. We think we would manage to trigger several builds but how do they return the build results to BitBucket?

          Michael Deckert added a comment - Hi uday reddy, may I get some more info of how to use the parametrized trigger plugin? What we want is to trigger several pipelines from one pull request. All of them shall return the build result to BitBucket. We think we would manage to trigger several builds but how do they return the build results to BitBucket?

          Daniel Beck added a comment -

          Is this a declarative pipeline?

          abayer PTAL – perhaps fallout from your "properties defined in the job" feature?

          Daniel Beck added a comment - Is this a declarative pipeline? abayer PTAL – perhaps fallout from your "properties defined in the job" feature?

          Andrew Bayer added a comment -

          Can you include the Jenkinsfiles and ideally the jobs' config.xmls, please?

          Andrew Bayer added a comment - Can you include the Jenkinsfiles and ideally the jobs' config.xmls, please?
          Christian Ditscher made changes -
          Attachment New: configOutput.xml [ 39171 ]
          Attachment New: configOutput2.xml [ 39172 ]

          danielbeck No, we do not use the declarative syntax (yet)

           

          Here are the (slightly adapted) Config files.

          configOutput.xml

          configOutput2.xml

          Christian Ditscher added a comment - danielbeck No, we do not use the declarative syntax (yet)   Here are the (slightly adapted) Config files. configOutput.xml configOutput2.xml
          Christian Ditscher made changes -
          Attachment Original: configOutput2.xml [ 39172 ]

            Unassigned Unassigned
            ditschi Christian Ditscher
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: