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

CVS update/checkout has sticky date set

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • cvs-plugin
    • None
    • Platform: All, OS: All

      Since 1.65 (I think...), Hudson does CVS update/checkout operations with sticky
      date. As a result, any commit operation done in the build ant of the software to
      be built will fail.

      This is what the console output says on checkout:

      [workspace] $ cvs -Q -z9 -d :pserver:user@server:2401/cvsroot co -D Tuesday,
      January 9, 2007 11:58:01 AM UTC moduleToCheckout

      And this is what happens when my build script tries to commit the resulting JARs:

      [cvs] cvs commit: Examining ../lib_frq
      [cvs] cvs commit: cannot commit with sticky date for file
      `../lib_frq/tapserver.jar'
      [cvs] cvs commit: cannot commit with sticky date for file
      `../lib_frq/tapserver_test.jar'
      [cvs] cvs [commit aborted]: correct above errors first!

      I figure that checkout/update with sticky date is something that some users
      might want, but I feel that there should be a switch to disable it for those who
      can't live with it.

            Unassigned Unassigned
            blackmuzzle blackmuzzle
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: