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

CVS changes returning duplicate entries

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Component/s: cvs-plugin
    • Labels:
    • Environment:
      Jenkins v1.602
      CVS Plug-in 2.12
    • Similar Issues:

      Description

      Using CVS plugin to get the nightly changes of my project is returning duplicate entries. It looks like it might be breaking the commit in smaller bunches of changes.

      I don't think that it is the correct behaviour, as the changes should return just one commit at time.

      For example, the changes page of my project is returning:

      Changes

      #75 (Mar 18, 2015 6:08:51 AM)

      Big commit - gerson23
      Big commit - gerson23
      Big commit - gerson23
      Big commit - gerson23
      Big commit - gerson23
      Big commit - gerson23
      Big commit - gerson23

      Although I have just one commit called Big commit, the page shows some, and each one has a different bunch of the files originally changed.

        Attachments

          Activity

          Hide
          mc1arke Michael Clarke added a comment -

          This is a general issue with CVS - commits are done by file rather than as a change-set with multiple files under a single commit potentially having different commit timestamps depending on how long CVS taks to process them. Trying to merge file commits into a single change-set may result in two different changes with the same commiter and commit message being merged into a single change incorrectly, so we only attempt to merge commits with an identical timestamp, user and commit comment.

          Show
          mc1arke Michael Clarke added a comment - This is a general issue with CVS - commits are done by file rather than as a change-set with multiple files under a single commit potentially having different commit timestamps depending on how long CVS taks to process them. Trying to merge file commits into a single change-set may result in two different changes with the same commiter and commit message being merged into a single change incorrectly, so we only attempt to merge commits with an identical timestamp, user and commit comment.
          Hide
          mc1arke Michael Clarke added a comment -

          Closing as "Won't Fix" since there's no 100% correct way of grouping commits

          Show
          mc1arke Michael Clarke added a comment - Closing as "Won't Fix" since there's no 100% correct way of grouping commits

            People

            • Assignee:
              mc1arke Michael Clarke
              Reporter:
              gerson23 Gerson Carlos
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: