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

Polling not working as intended using CVS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • cvs-plugin
    • None
    • Linux (Ubuntu), Windows (all platforms)

      Hi,

      Long time (Hudson) user, first-time reporter.

      Hudson ver: 1.347
      OS: Linux vbuild05 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/Linux
      CVS: Concurrent Versions System (CVS) 1.12.13 (client/server)

      Here is the issue.

      Console Output:

      "
      ...
      P src/NBBuilderRun.cpp
      P inc/SyCLib.h
      P src/SyCLib.cpp
      $ no changes detected
      ...
      "

      However, CVS Polling Log shows:

      "
      ...
      Done. Took 2 min 47 sec
      Changes found
      "

      As we can see, Hudson is fetching cvs checkouts, but reporting that there are no changes. At the same time, it doesn't update the 'changelog.xml' file in the 'builds' dir.

      changelog.xml contents:

      $ more changelog.xml
      <changelog/>

      If you need any other info, please let me know. This is a blocker for us. I hope somebody would kindly look into it.

      Thanks so much!

          [JENKINS-5744] Polling not working as intended using CVS

          babushka created issue -

          afarentino added a comment - - edited

          I'm still seeing this issue as well on my Jenkins CI server (currently at Jenkins ver. 1.400). The core bug usually presents itself in the following order:
          A CVS polling operation completes and detects changes triggering a build of a job.
          The build runs, performs a cvs update of files that have changed but when the build job finishes the jenkins job specific UI reports no changes in the changelog.

          I see this bug was reported over a year ago but noticed that zero activity has occured on it so I decided to vote it up one.

          On a secondary note, it looks like progress is already underway on integrating in a self-contained cvs client library. It seems like that issue could be considered a blocker for this fix as it significantly would alter the way the cvs plugin interacts with the system....

          afarentino added a comment - - edited I'm still seeing this issue as well on my Jenkins CI server (currently at Jenkins ver. 1.400). The core bug usually presents itself in the following order: A CVS polling operation completes and detects changes triggering a build of a job. The build runs, performs a cvs update of files that have changed but when the build job finishes the jenkins job specific UI reports no changes in the changelog. I see this bug was reported over a year ago but noticed that zero activity has occured on it so I decided to vote it up one. On a secondary note, it looks like progress is already underway on integrating in a self-contained cvs client library. It seems like that issue could be considered a blocker for this fix as it significantly would alter the way the cvs plugin interacts with the system....
          afarentino made changes -
          URL New: http://issues.hudson-ci.org/browse/HUDSON-49?page=com.atlassian.streams.streams-jira-plugin%3Aactivity-stream-issue-tab
          Environment Original: Linux (Ubuntu) New: Linux (Ubuntu), Windows (all platforms)
          afarentino made changes -
          Link New: This issue is blocking JENKINS-49 [ JENKINS-49 ]
          afarentino made changes -
          Link New: This issue depends on JENKINS-49 [ JENKINS-49 ]
          afarentino made changes -
          Link Original: This issue is blocking JENKINS-49 [ JENKINS-49 ]

          btrim added a comment -

          I've seen something like this, except I'm usually only missing some changes, and usually only from commits via eclipse vs cli.

          btrim added a comment - I've seen something like this, except I'm usually only missing some changes, and usually only from commits via eclipse vs cli.

          Sagar Khushalani added a comment -

          We have a similar issue, except in our case, there is no change and jenkins still detects a change, checks-out everything, and builds - over and over. Obviously, in our case, the change log is blank, because there are no changes.

          Sagar Khushalani added a comment - We have a similar issue, except in our case, there is no change and jenkins still detects a change, checks-out everything, and builds - over and over. Obviously, in our case, the change log is blank, because there are no changes.
          Michael Clarke made changes -
          Assignee New: Michael Clarke [ mc1arke ]

            mc1arke Michael Clarke
            babushka babushka
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: