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

Recent Changes are not accurate with Clearcase UCM

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: clearcase-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All

      Description

      I have one job configured to create a new view and extract the whole source code
      tree for every build (this takes about 25 minutes). The clearcase plugin
      determines the recent changes after finishing loading the source code. Since the
      recent changes are determined based on time, by the time it calculates the
      changes (25 min after started loading the source code), there are already some
      changes that were delivered to the SCM repository but were not extracted for
      this build. These changes show up in the recent changes of a build, although
      that code is not there.

        Issue Links

          Activity

          Hide
          davidmc24 davidmc24 added a comment -

          CC'ing

          Show
          davidmc24 davidmc24 added a comment - CC'ing
          Hide
          kajays kajays added a comment -

          I am using clearcase plugin version 0.8.4. I am having just opposit situation.
          The code is loaded in the workspace but change log doesnot shows some changes. I am using the snapshot view and even its log shows the file is loading but somehow the change list miss the file.

          Show
          kajays kajays added a comment - I am using clearcase plugin version 0.8.4. I am having just opposit situation. The code is loaded in the workspace but change log doesnot shows some changes. I am using the snapshot view and even its log shows the file is loading but somehow the change list miss the file.
          Hide
          lipsestraat lipsestraat added a comment -

          A good fix for this issue would be to parse the output of the 'update view' command to determine the list of changes. (Iso issuing a separate command to determine the same list).

          A fix that would e.g. take some time difference between the 'update view' and the 'lshistory' into account would be flawed, since you can also have multi-site installations which could update the VOB between both commands, which would again generate differences between the shown differences and the actual differences.

          Show
          lipsestraat lipsestraat added a comment - A good fix for this issue would be to parse the output of the 'update view' command to determine the list of changes. (Iso issuing a separate command to determine the same list). A fix that would e.g. take some time difference between the 'update view' and the 'lshistory' into account would be flawed, since you can also have multi-site installations which could update the VOB between both commands, which would again generate differences between the shown differences and the actual differences.
          Hide
          vlatombe Vincent Latombe added a comment -

          This is an excellent idea. Even better, the log entry of the update (which is currently redirected to NUL) could be used (as far as I remember, it only contains the changelog). However, lshistory would still be needed because we need the author and activity, but it would be way better.

          Show
          vlatombe Vincent Latombe added a comment - This is an excellent idea. Even better, the log entry of the update (which is currently redirected to NUL) could be used (as far as I remember, it only contains the changelog). However, lshistory would still be needed because we need the author and activity, but it would be way better.
          Hide
          vlatombe Vincent Latombe added a comment -

          I moved up the changelog logic. It is now done just before the clearcase update.

          It is currently in trunk and needs testing.

          Show
          vlatombe Vincent Latombe added a comment - I moved up the changelog logic. It is now done just before the clearcase update. It is currently in trunk and needs testing.
          Hide
          vlatombe Vincent Latombe added a comment -

          Fixed since 1.3

          Show
          vlatombe Vincent Latombe added a comment - Fixed since 1.3

            People

            • Assignee:
              vlatombe Vincent Latombe
              Reporter:
              slider3 slider3
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: