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

Job parameters appear in multiple jobs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            ditschi Christian Ditscher created issue -
            ditschi Christian Ditscher made changes -
            Field Original Value New Value
            Description 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.
            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.
            ditschi Christian Ditscher made changes -
            Priority Major [ 3 ] Blocker [ 1 ]
            ditschi Christian Ditscher made changes -
            Attachment configOutput.xml [ 39171 ]
            Attachment configOutput2.xml [ 39172 ]
            ditschi Christian Ditscher made changes -
            Attachment configOutput2.xml [ 39172 ]
            ditschi Christian Ditscher made changes -
            Attachment configOutput2.xml [ 39173 ]
            ditschi Christian Ditscher made changes -
            Attachment 2017-08-29_15h51_02.png [ 39532 ]
            danielbeck Daniel Beck made changes -
            Component/s git-plugin [ 15543 ]
            danielbeck Daniel Beck made changes -
            Component/s core [ 15593 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-39495 [ JENKINS-39495 ]

              People

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

                Dates

                Created:
                Updated: