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

Bitbucket Plugin - Triggers the pipeline even when the repo is not configured with webhook

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Bitbucket Plugin - Triggers the Jenkins pipeline even when the repo is not configured with webhook. This happening only when we are using two or more different repos in the pipeline.

      Consider:

      We have two Bitbucket repos A and B one for hosting Codes and another one for hosting Build and Deployment scripts. (Devops related)

      1. Jenkins Pipeline - Configured to use Jenkinsfile from SCM in our case Repo A and Branch develop
      2. Jenkinsfile in turn will clone the Repo B for build and deployments scripts while pipeline is running using checkout step
      3. Repo A is configured with Webhook and Repo B is not configured with Webhook.

      Steps to Reproduce:

      1. Commit something in the develop branch of Repo A and its trigger the pipeline as expected. No issue.
      2. Commit Something in the Repo B. No triggers since it was not configured with Webhook and its expected no issue.
      3. Now Commit something in the different branch of Repo A and its trigger the pipeline since there is change in the Repo B. I verified this in the Bitbucket Webhook log.

      What we are expecting:

      Whenever there is a change in develop branch of Repo A it can trigger the pipeline. But it should not trigger the pipeline for other Branches for Repo A or other Repos itself.

       

        Attachments

        1. bitbucketpush.log
          1 kB
        2. jenkins.log
          25 kB
        3. push.log
          12 kB

          Activity

          satheeshpayoda SatheeshP created issue -
          satheeshpayoda SatheeshP made changes -
          Field Original Value New Value
          Description Bitbucket Plugin - Triggers the Jenkins pipeline even when the repo is not configured with webhook. This happening only when we are using two or more different repos in the pipeline.

          *Consider:*

          We have two Bitbucket repos A and B one for hosting Codes and another one for hosting Build and Deployment scripts. (Devops related)
           # Jenkins Pipeline - Configured to use Jenkinsfile from SCM in our case *Repo A* and Branch *develop*
           # Jenkinsfile in turn will clone the *Repo B* for build and deployments scripts while pipeline is *running* using *checkout* step
           # *Repo A* is configured with Webhook and *Repo B is not* configured with Webhook.

          *Steps to Reproduce:*
           # Commit something in the *develop* branch of *Repo A* and its trigger the pipeline as expected. No issue.
           # Commit Something in the *Repo B.* No triggers since it was not configured with Webhook and its expected no issue.
           # Now Commit something in the *different* *branch* of *Repo A* and its trigger the pipeline since there is change in the *Repo B.* I verified this in the Bitbucket Webhook log.

          *What we are expecting:*

          Whenever there is a change in *develop* branch of *Repo A* it can ** trigger the pipeline. But it should not trigger the pipeline for *other Branches for Repo A* or *other Repos itself.*

           
          Bitbucket Plugin - Triggers the Jenkins pipeline even when the repo is not configured with webhook. This happening only when we are using two or more different repos in the pipeline.

          *Consider:*

          We have two Bitbucket repos A and B one for hosting Codes and another one for hosting Build and Deployment scripts. (Devops related)
           # Jenkins Pipeline - Configured to use Jenkinsfile from SCM in our case *Repo A* and Branch *develop*
           # Jenkinsfile in turn will clone the *Repo B* for build and deployments scripts while pipeline is *running* using *checkout* step
           # *Repo A* is configured with Webhook and *Repo B is not* configured with Webhook.

          *Steps to Reproduce:*
           # Commit something in the *develop* branch of *Repo A* and its trigger the pipeline as expected. No issue.
           # Commit Something in the *Repo B.* No triggers since it was not configured with Webhook and its expected no issue.
           # Now Commit something in the *different* *branch* of *Repo A* and its trigger the pipeline since there is change in the *Repo B.* I verified this in the Bitbucket Webhook log.

          *What we are expecting:*

          Whenever there is a change in *develop* branch of *Repo A* it can trigger the pipeline. But it should not trigger the pipeline for *other Branches for Repo A* or *other Repos itself.*

           
          tzach_solomon Tzach Solomon made changes -
          Assignee Tzach Solomon [ tzach_solomon ]
          satheeshpayoda SatheeshP made changes -
          Attachment bitbucketpush.log [ 54815 ]
          Attachment jenkins.log [ 54816 ]
          satheeshpayoda SatheeshP made changes -
          Attachment bitbucketpush.log [ 54815 ]
          satheeshpayoda SatheeshP made changes -
          Attachment jenkins.log [ 54816 ]
          satheeshpayoda SatheeshP made changes -
          Attachment bitbucketpush.log [ 54817 ]
          Attachment jenkins.log [ 54818 ]
          satheeshpayoda SatheeshP made changes -
          Attachment push.log [ 54839 ]

            People

            Assignee:
            tzach_solomon Tzach Solomon
            Reporter:
            satheeshpayoda SatheeshP
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: