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

cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: cvs-plugin
    • Labels:
      None
    • Environment:
      suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6
    • Similar Issues:

      Description

      When checking out a cvs repository with Branch and Use HEAD revision if tag not found, the Changes list is always empty even though the build was triggered by scm changes that are picked up the by cvs update in the build log.

      Since the use Head function was introduced by me in 1.5, maybe the update check is broken in a way I didn't notice, I will try to fix this.

        Attachments

          Activity

          Hide
          alexlehm Alex Lehmann added a comment -

          I still have the problem in the 2.1 plugin, the files that are not in the branch are not picked up by rlog and the changes are not noticed

          Building in workspace /home/lehmann/.jenkins/jobs/cvstest/workspace
          cvs update -d -P -f -r BRANCHTEST workspace
          cvs update: Updating workspace
          U workspace/branch1
          U workspace/branch2
          cvs rlog: Logging home/lehmann/cvstest
          cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
          cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
          cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
          Finished: SUCCESS

          (files named branch* are branched, files name file* are not)

          Show
          alexlehm Alex Lehmann added a comment - I still have the problem in the 2.1 plugin, the files that are not in the branch are not picked up by rlog and the changes are not noticed Building in workspace /home/lehmann/.jenkins/jobs/cvstest/workspace cvs update -d -P -f -r BRANCHTEST workspace cvs update: Updating workspace U workspace/branch1 U workspace/branch2 cvs rlog: Logging home/lehmann/cvstest cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file1,v' cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file2,v' cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file3,v' Finished: SUCCESS (files named branch* are branched, files name file* are not)
          Hide
          alexlehm Alex Lehmann added a comment -

          issue is still present or appeared again in 2.1

          Show
          alexlehm Alex Lehmann added a comment - issue is still present or appeared again in 2.1
          Hide
          mc1arke Michael Clarke added a comment -

          Can you run the following command and paste the output here: cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rBRANCHTEST cvstest (change the dates to match the start time of your previous builds)?

          Show
          mc1arke Michael Clarke added a comment - Can you run the following command and paste the output here: cvs rlog -d"22 Mar 2012 09:26:21 -0400<27 Mar 2012 12:00:00 -0400" -S -rBRANCHTEST cvstest (change the dates to match the start time of your previous builds)?
          Hide
          alexlehm Alex Lehmann added a comment - - edited

          $ cvs rlog -d"14 Feb 2012 09:26:21 +0100<27 Mar 2012 12:00:00 +0100" -S -rBRANCHTEST home/lehmann/cvstest
          cvs rlog: Logging home/lehmann/cvstest

          RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
          head: 1.3
          branch:
          locks: strict
          access list:
          symbolic names:
          BRANCHTEST: 1.1.0.2
          keyword substitution: kv
          total revisions: 6; selected revisions: 1
          description:
          ----------------------------
          revision 1.1.2.3
          date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1; commitid: 100d4f69af6e4567;
          cvstest
          =============================================================================
          cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
          cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
          cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file3,v'

          Show
          alexlehm Alex Lehmann added a comment - - edited $ cvs rlog -d"14 Feb 2012 09:26:21 +0100<27 Mar 2012 12:00:00 +0100" -S -rBRANCHTEST home/lehmann/cvstest cvs rlog: Logging home/lehmann/cvstest RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v head: 1.3 branch: locks: strict access list: symbolic names: BRANCHTEST: 1.1.0.2 keyword substitution: kv total revisions: 6; selected revisions: 1 description: ---------------------------- revision 1.1.2.3 date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1; commitid: 100d4f69af6e4567; cvstest ============================================================================= cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file1,v' cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file2,v' cvs rlog: warning: no revision `BRANCHTEST' in `/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
          Hide
          mc1arke Michael Clarke added a comment -

          This should be resolved in the latest snapshot with the fixes for failing to poll or recognise changes on branches

          Show
          mc1arke Michael Clarke added a comment - This should be resolved in the latest snapshot with the fixes for failing to poll or recognise changes on branches

            People

            • Assignee:
              mc1arke Michael Clarke
              Reporter:
              alexlehm Alex Lehmann
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: