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

git exclusion incorrectly excludes a commit author that was not in exclusion list

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • git-plugin
    • None
    • jenkins 1.520

      We have several projects connected to git repositories, polling the scm on various cron schedules.

      One of the projects is set to build master every hour on the hour if source has changed, ignoring commits by several users (see job-configuration.jpg).

      If you look at attached git-polling-log.jpg, it shows that commit 2358fb1 found an excluded author. That is not the case. 2358fb1 was authored by dmaskew (from git-commit-log.jpg), who is not in the exclude list for the repository. However, both d07969c and 4f6f07b have authors that are in the exclude list.

      This works fine for other jobs. Something we're doing wrong here?

          [JENKINS-19378] git exclusion incorrectly excludes a commit author that was not in exclusion list

          Which version of git-client are you using ? This may be caused by a collision between two subsequent commit parsing the changelog.
          I have plan to revisit this component to use --format and get a more predictible output.

          Nicolas De Loof added a comment - Which version of git-client are you using ? This may be caused by a collision between two subsequent commit parsing the changelog. I have plan to revisit this component to use --format and get a more predictible output.

          Curtis Wilson added a comment -

          We were able to workaround this by setting the "force polling from workspace" option

          Curtis Wilson added a comment - We were able to workaround this by setting the "force polling from workspace" option

            Unassigned Unassigned
            cwilso1 Curtis Wilson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: