[JIRA] [cvs] (JENKINS-18522) Cannot check out CVS module using legacy mode

Thu, 27 Jun 2013 10:55:23 -0700

Scott Telle commented on Bug JENKINS-18522

As for my issue, I think it's resolved... I still agree with John regarding an option to use an external .exe, but that's probably better covered in the other issue.

My resolution for anyone else:

I was using aliases in the CVSROOT\modules file that was creating a directory structure like so:

# CVSROOT\modules
My.Application -a Applications/bin Applications/MyApplication Libraries/Library1 Libraries/Library2

# Result:
Applications/
  bin/
  MyApplication/
Libraries/
  Library1/
  Library2/

This can be reproduced by just adding each of the aliases above into the modules box in Jenkins. This is actually simpler to set up - versus creating a module that handled this for us.

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to