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

The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • cvs-plugin
    • SUSE Linux Enterprise Server 11 SP2 on x86-64

      Bug found using the Jenkins CVS-Plugin version 2.6:
      The detection for changes for a CVS SCM is actually made with the cvs rlog command.
      The cvs rlog command does not set the revision option (-r) when polling HEAD or any other branches.
      If no -r option is applied all changes of all branches are detected!
      The cvs rlog option -r<branch> has always to be appended.
      If the Head is configured cvs rlog command has to use -rHEAD.

          [JENKINS-15416] The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected

          Daniel Fischer created issue -
          Daniel Fischer made changes -
          Attachment New: JENKINS-15416.zip [ 22627 ]
          Daniel Fischer made changes -
          Daniel Fischer made changes -
          Summary Original: The CVS changes detector always does no filtering on selected branch or tag New: The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected
          Michael Clarke made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Michael Clarke made changes -
          Assignee New: Michael Clarke [ mc1arke ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Daniel Fischer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 146150 ] New: JNJira + In-Review [ 206193 ]

            mc1arke Michael Clarke
            hidminds Daniel Fischer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: