CVS Checkout Does Not Get Latest Revision

Still need help?

The Atlassian Community is here for you.

Ask the community


When performing a checkout in CVS during a build, Bamboo does not get the latest revision from the repository.  The -D flag will also appear in the build_logs:

simple	03-Sep-2013 14:21:25	Starting task 'Checkout Default Repository' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.checkout'
simple	03-Sep-2013 14:21:25	Updating source code to revision: 2013-08-20 17:23:15 -0700
command	03-Sep-2013 14:21:25	Running CVS command: 'update -d -P -kb -D 2013-08-20 17:23:15 -0700 '\n             ... in: '/bamboo/home/warbamboo501/xml-data/build-dir/TEST-CVS-JOB1/newmodule'\n        ... CVSROOT: '/bamboo/cvs/cvsrepo'
simple	03-Sep-2013 14:21:25	Updated source code to revision: 2013-08-20 17:23:15 -0700


Bamboo is using sticky tags during CVS checkouts that specify a date or time prior to the newest revision checkin.


  1. Enable Force Clean Build in the Source Code Checkout task in your plan.
  2. Add the -DCVS_FORCE_CHECKOUT_TO_LATEST=true system property to JAVA_OPTS:
  • For instance running in a Jetty wrapper, edit the <bamboo-install>/conf/wrapper.conf to add property as per this example using the default wrapper.conf:
  • For instance running Tomcat, you must add the parameter to your JAVA_OPTS. The steps are outlines in the Bamboo EAR-WAR installation guide.
Last modified on Mar 30, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.