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

False positive on git polling

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • core
    • None
    • - Jenkins deployed on Jboss AS 7.1.1
      - Linux CentOs

      The Git Polling gives a false positive trigger for changes, the log:

      No existing build. Scheduling a new one.
Done. Took 0 ms
Changes found

      And the job Console Output shows that no changes was found:

      Started by an SCM change
Building in workspace /opt/jboss-as/.jenkins/workspace/test-service
Checkout:test-service / /opt/jboss-as/.jenkins/workspace/test-service - hudson.remoting.LocalChannel@4f13750
Using strategy: Default
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision d87a4057e85c5413ff529c6cc16e49ab90ea9573 (origin/master)
Checking out Revision d87a4057e85c5413ff529c6cc16e49ab90ea9573 (origin/master)
No change to record in branch origin/master

            ndeloof Nicolas De Loof
            douglasdedo Douglas Mendonca
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: