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

Scan Organization Folder not detecting code changes

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • pipeline, scm-api-plugin
    • None
    • Jenkins 2.109

      My scan organization folder is set to execute every 1 minutes.  It runs fine but is not detecting code changes and building my changes.  If i access the configure option and make a change to the configuration, that forces a scan, and my programs build.  Worked fine in 2.79

        1. Jenkinsfile
          6 kB
        2. job.config.xml
          4 kB
        3. org.config.xml
          3 kB
        4. Screen Shot 2018-03-01 at 8.49.32 AM.png
          Screen Shot 2018-03-01 at 8.49.32 AM.png
          105 kB

          [JENKINS-49798] Scan Organization Folder not detecting code changes

          Mark Waite added a comment -

          kford2000 I think others will need more information before they can assist with diagnosis. For example:

          • Which branch source plugin are you using? GitHub, Bitbucket, Gitea, or Git
          • If you're using the Git branch source, are you using modern or legacy SCM provider?
          • Are there entries in the Jenkins log which might hint why the build did not run?
          • Are there any reports in logs that you've exhausted your API limits with your git hosting provider?

          Mark Waite added a comment - kford2000 I think others will need more information before they can assist with diagnosis. For example: Which branch source plugin are you using? GitHub, Bitbucket, Gitea, or Git If you're using the Git branch source, are you using modern or legacy SCM provider? Are there entries in the Jenkins log which might hint why the build did not run? Are there any reports in logs that you've exhausted your API limits with your git hosting provider?

          Kevin Ford added a comment - - edited
          • Using Bitbucket installed on local server as well as jenkins on local server, all this worked on version 2.79, all broke when i install 3.10
          • Not sure what you are asking
          • which log files
          • attached my jenkinsfile

           

          Definitely could webex with someone to help work through this issue ^^ 

          Kevin Ford added a comment - - edited Using Bitbucket installed on local server as well as jenkins on local server, all this worked on version 2.79, all broke when i install 3.10 Not sure what you are asking which log files attached my jenkinsfile Jenkinsfile   Definitely could webex with someone to help work through this issue ^^ 

          Mark Waite added a comment -

          The branch source provider is defined in the multi-branch job definition. Since you were willing to upload your Jenkinsfile, could you also upload the config.xml file for the multi-branch PIpeline job? I suspect that will be needed if someone investigates it.

          I doubt very much that anyone will agree to a webex to investigate the issue. That's quite uncommon in open source projects.

          Mark Waite added a comment - The branch source provider is defined in the multi-branch job definition. Since you were willing to upload your Jenkinsfile, could you also upload the config.xml file for the multi-branch PIpeline job? I suspect that will be needed if someone investigates it. I doubt very much that anyone will agree to a webex to investigate the issue. That's quite uncommon in open source projects.

          Kevin Ford added a comment -

          org.config.xml - Organization level config

          job.config.xml - Job level config

           

          Kevin Ford added a comment - org.config.xml  - Organization level config job.config.xml  - Job level config  

          Mark Waite added a comment -

          kford2000 I believe the guidance from stephenconnolly and others is that web hooks should be configured from the provider (Bitbucket in your case) to notify Jenkins when a commit is pushed, rather than checking for changes as frequently as once a minute. I think his heuristic suggested that the check for changes is a "safety" in case one of the webhooks is missed. At once a minute, it seems like you're making the check for changes into the primary way of detecting changes.

          Mark Waite added a comment - kford2000 I believe the guidance from stephenconnolly and others is that web hooks should be configured from the provider (Bitbucket in your case) to notify Jenkins when a commit is pushed, rather than checking for changes as frequently as once a minute. I think his heuristic suggested that the check for changes is a "safety" in case one of the webhooks is missed. At once a minute, it seems like you're making the check for changes into the primary way of detecting changes.

          Kevin Ford added a comment -

          Tried that first on earlier versions, with errors so this approach fixed.  Trying it again and attaching the error.  Maybe i can get some direction on how to fix, no luck so far from my research.

          Kevin Ford added a comment - Tried that first on earlier versions, with errors so this approach fixed.  Trying it again and attaching the error.  Maybe i can get some direction on how to fix, no luck so far from my research.

          Kevin Ford added a comment -

          In my attempts, it appears that webhooks and Bitbucket team projects do not work together.  Any advise to what i am missing????

          Kevin Ford added a comment - In my attempts, it appears that webhooks and Bitbucket team projects do not work together.  Any advise to what i am missing????

          Mark Waite added a comment -

          Unfortunately, I don't have any experience with Bitbucket webhooks. You might ask on the Internet Relay Chat channel or on the Jenkins Users mailing list. The number of people who read git plugin bug reports is much smaller than the number of people who read either of those channels.

          Mark Waite added a comment - Unfortunately, I don't have any experience with Bitbucket webhooks. You might ask on the Internet Relay Chat channel or on the Jenkins Users mailing list. The number of people who read git plugin bug reports is much smaller than the number of people who read either of those channels.

          Mat Jaggard added a comment -

          I have also upgraded and found this issue. The hooks and webhooks don't seem to work. I followed this guide but the screenshots are not the same any more so I couldn't enter the same data, and also I got an error about missing a crumb because we have CSRF protection enabled and I do not control the Jenkins server so cannot turn it off.

          Mat Jaggard added a comment - I have also upgraded and found this issue. The hooks and webhooks don't seem to work. I followed this guide but the screenshots are not the same any more so I couldn't enter the same data, and also I got an error about missing a crumb because we have CSRF protection enabled and I do not control the Jenkins server so cannot turn it off.

          Mat Jaggard added a comment -

          Mat Jaggard added a comment - https://mohamicorp.atlassian.net/wiki/spaces/DOC/pages/85065729/Webhook+To+Jenkins+for+Bitbucket

            Unassigned Unassigned
            kford2000 Kevin Ford
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: