Steps:

  • Create a Job for a CVS branch (see configuration below).
  • Commit some changes directly to the branch -> Jenkins will trigger a build once the polling was done.
  • To get a change from HEAD to the branch, move the branch tag (we "merge" our changes to the branch by moving the branch tag, if possible) -> the polling will not discover any changes.

This worked in old versions which used 'cvs update' for polling.

The CVS rlog output shows nothing, since it doesn't find any changes on the branch (excepted the change was commit directly on the branch, then it works)

Started on 05.09.2012 14:01:24
cvs rlog -S -d05 Sep 2012 12:03:00 +0200<05 Sep 2012 14:01:24 +0200 WISKI/java
cvs rlog: Logging WISKI/java
cvs rlog: Logging WISKI/java/base
...
Done. Took 43 Sekunden
No changes

Here's the job config:

...
<scm class="hudson.scm.CVSSCM">
<flatten>true</flatten>
<repositories>
<hudson.scm.CvsRepository>
<cvsRoot>:pserver:xxx@xxx:/cvssrc</cvsRoot>
<repositoryItems>
<hudson.scm.CvsRepositoryItem>
<modules>
<hudson.scm.CvsModule>
<localName></localName>
<remoteName>WISKI/java</remoteName>
</hudson.scm.CvsModule>
</modules>
<location class="hudson.scm.CvsRepositoryLocation$BranchRepositoryLocation">
<locationType>BRANCH</locationType>
<locationName>Br_Release_WISKI7_7_2_1</locationName>
<useHeadIfNotFound>false</useHeadIfNotFound>
</location>
</hudson.scm.CvsRepositoryItem>
</repositoryItems>
<compressionLevel>-1</compressionLevel>
<excludedRegions>
<hudson.scm.ExcludedRegion>
<pattern></pattern>
</hudson.scm.ExcludedRegion>
</excludedRegions>
<password>xxx</password>
<passwordRequired>true</passwordRequired>
</hudson.scm.CvsRepository>
</repositories>
<canUseUpdate>true</canUseUpdate>
<skipChangeLog>false</skipChangeLog>
<pruneEmptyDirectories>true</pruneEmptyDirectories>
<disableCvsQuiet>false</disableCvsQuiet>
<cleanOnFailedUpdate>true</cleanOnFailedUpdate>
</scm>
...
<triggers class="vector">
<hudson.triggers.SCMTrigger>
<spec>0 * * * *</spec>
</hudson.triggers.SCMTrigger>
</triggers>
...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to