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

GIT changelog shows all changes since first day

    Details

    • Similar Issues:

      Description

      Since installing GIT Client plugin version 1.1 (and updated 1.1.1), Jenkins job now shows all changes since we started with GIT. See the attached picture (there is about 500 changes). It's quite annoying problem. All is OK after replacing the actual GIT Client plugin (1.1.1) with version 1.0.7. It's good workaround, but definitely not a permanent solution

      The job we are using consists of two building slaves. And the interesting point is, that the change log looks fine on 64bit slave (only changes since the previous build are shown), but on 32bit slave (and Jenkins Master machine) it shows all changes since start.

      Feel free to contact me in case you need more details.

        Attachments

          Issue Links

            Activity

            Hide
            tony_bridges Tony Bridges added a comment -

            I am seeing the same problem, except that my changelist is about 6000 items long. This causes all kinds of problems. I'm rolling back to a previous version to get around the problem, as suggested. Any update from the author regarding a fix for the issue ?

            Show
            tony_bridges Tony Bridges added a comment - I am seeing the same problem, except that my changelist is about 6000 items long. This causes all kinds of problems. I'm rolling back to a previous version to get around the problem, as suggested. Any update from the author regarding a fix for the issue ?
            Hide
            joefitzgerald Joe Fitzgerald added a comment -

            I can also confirm this issue in 1.1.1 and 1.1.2 on Windows.

            Show
            joefitzgerald Joe Fitzgerald added a comment - I can also confirm this issue in 1.1.1 and 1.1.2 on Windows.
            Hide
            ndeloof Nicolas De Loof added a comment -

            git-client 1.0.x used
            git whatchanged --no-abbrev -M --pretty=raw revFrom..refTo

            git-client 1.1.x use
            git whatchanged --no-abbrev -M --pretty=raw ^revFrom refTo

            "<commit1>..<commit2>" is a short-hand notation for "^<commit1> <commit2>" so should be strictly equivalent - maybe a git bug running on windows ? Can you try both commands from command line to confirm ?

            Show
            ndeloof Nicolas De Loof added a comment - git-client 1.0.x used git whatchanged --no-abbrev -M --pretty=raw revFrom..refTo git-client 1.1.x use git whatchanged --no-abbrev -M --pretty=raw ^revFrom refTo "<commit1>..<commit2>" is a short-hand notation for "^<commit1> <commit2>" so should be strictly equivalent - maybe a git bug running on windows ? Can you try both commands from command line to confirm ?
            Hide
            odklizec Pavel Kudrys added a comment - - edited

            Hello Nicolas,

            Thank you for your reply!

            I tried both lines and sure enough, the first one returns only the changes in "from-to" revision range (tested with git version 1.8.1 and 1.8.3). Is there a reason why the version 1.1.x don't use .. in from..to definition? I just checked the git-whatchanged manual and there is also used .. between <since> and <until> range definition. So it seems to be the "standard" way?

            Show
            odklizec Pavel Kudrys added a comment - - edited Hello Nicolas, Thank you for your reply! I tried both lines and sure enough, the first one returns only the changes in "from-to" revision range (tested with git version 1.8.1 and 1.8.3). Is there a reason why the version 1.1.x don't use .. in from..to definition? I just checked the git-whatchanged manual and there is also used .. between <since> and <until> range definition. So it seems to be the "standard" way?
            Hide
            sklapp Sebastian Klapp added a comment -

            Ran into the same problem today.

            Using the plugin we call a batch file that redirects to cygwins git.exe after some magic.
            In windows the caret (^) is an escaping character for the command line and is removed when calling a batch file so the caret is lost.
            The problem has neither to do with git nor with the jenkins plugin.

            Show
            sklapp Sebastian Klapp added a comment - Ran into the same problem today. Using the plugin we call a batch file that redirects to cygwins git.exe after some magic. In windows the caret (^) is an escaping character for the command line and is removed when calling a batch file so the caret is lost. The problem has neither to do with git nor with the jenkins plugin.
            Hide
            mikel1982 Michal Letynski added a comment -

            We have same problem. Any plans to fix it ? It looks like its a duplication of @JENKINS-18125

            Show
            mikel1982 Michal Letynski added a comment - We have same problem. Any plans to fix it ? It looks like its a duplication of @ JENKINS-18125
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Nicolas De Loof
            Path:
            src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
            http://jenkins-ci.org/commit/git-client-plugin/b19566dcbffbdc4e62e3bef115472171cafcf365
            Log:
            [FIXED JENKINS-18995] sanitize command that include '^' character

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/b19566dcbffbdc4e62e3bef115472171cafcf365 Log: [FIXED JENKINS-18995] sanitize command that include '^' character

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                odklizec Pavel Kudrys
              • Votes:
                1 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: