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

Gerrit-Trigger-Plugin Bug on 'Enable Topic Association' , which triggers unnecessary jobs by patches which already MERGED.

    XMLWordPrintable

Details

    • Feature released in Gerrit Trigger Plugin vers. 2.38.0

    Description

       

      Situation:

       

      Say I have 3 patches with same topic, patch A, patch B, patch C and their status below,

       

      Patch A:  status: merged, branch: develop

      Patch B:  status: merged, branch: develop

      Patch C :  status: open, branch: release

       

       On patch C, I reply some key word to trigger only a target job name job_A. However, with the Enable Topic Association enabled, I am end up triggering some other unnecessary jobs besides job_A just because they are labeled with the same topic regardless of different branch.  This is definitely NOT an expected behavior.    

       

       

      Attachments

        Issue Links

          Activity

            kentchen01 kentchen01 kentchen01 created issue -
            kentchen001 chen made changes -
            Field Original Value New Value
            Summary Gerrit-Trigger-Plugin Bug on 'Enable Topic Association' , triggers necessary jobs by merged patches Gerrit-Trigger-Plugin Bug on 'Enable Topic Association' , which triggers unnecessary jobs by patches which already MERGED.
            kentchen001 chen made changes -
            Description  

            Situation:

             

            Say I have 3 patches with same topic, patch A, patch B, patch C and their status below,

             

            Patch A:  status: merged, branch: develop

            Patch B:  status: merged, branch: develop

            Patch C :  status: open, branch: release

             

             On patch C, I reply some key word to trigger only a target job name job_A. However, with the Enable Topic Association enabled, I am end up triggering some other jobs besides job_A because of the same topic regardless of different branch.  This is definetely an unexpected behavior.    

             

             
            kentchen001 chen made changes -
            Description  

            Situation:

             

            Say I have 3 patches with same topic, patch A, patch B, patch C and their status below,

             

            Patch A:  status: merged, branch: develop

            Patch B:  status: merged, branch: develop

            Patch C :  status: open, branch: release

             

             On patch C, I reply some key word to trigger only a target job name job_A. However, with the Enable Topic Association enabled, I am end up triggering some other jobs besides job_A because of the same topic regardless of different branch.  This is definetely an unexpected behavior.    

             

             
             

            Situation:

             

            Say I have 3 patches with same topic, patch A, patch B, patch C and their status below,

             

            Patch A:  status: merged, branch: develop

            Patch B:  status: merged, branch: develop

            Patch C :  status: open, branch: release

             

             On patch C, I reply some key word to trigger only a target job name job_A. However, with the *Enable Topic Association enabled*, I am end up triggering some other unnecessary jobs besides job_A just because they are labeled with the same topic regardless of different branch.  This is definitely NOT an expected behavior.    

             

             
            ckreisl ckreisl made changes -
            Link This issue duplicates JENKINS-70111 [ JENKINS-70111 ]
            ckreisl ckreisl made changes -
            Released As Feature released in Gerrit Trigger Plugin vers. 2.38.0
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Fixed but Unreleased [ 10203 ]
            ckreisl ckreisl made changes -
            Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]

            People

              kentchen01 kentchen01 kentchen01
              kentchen01 kentchen01 kentchen01
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: