In Perforce, you cannot sync based on a branch spec name. A branch spec is basically just a mapping from repository location A to repository location B and says nothing about file revisions. You sync based on a valid revision identifier. A label, date, "#head" are valid revision identifiers.
Basically just put your label in there and it should work fine. > -----Original Message----- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Friday, June 30, 2006 10:09 AM > To: [email protected] > Cc: Mike Perham > Subject: Re: How to have project pull specific label from SCM? > > yes, it's the field to use. Do you know if the Perforce > command is different if it's a label or a > branch? > > Emmanuel > > Karr, David a écrit : > > There is a field labeled "Scm Branch/Tag". Is that where I > put the label name? How would it know this is a label and > not a branch? > > > >> -----Original Message----- > >> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > >> Sent: Friday, June 30, 2006 12:54 AM > >> To: [email protected] > >> Subject: Re: How to have project pull specific label from SCM? > >> > >> You can define the label/branch in the project view (click on > >> the edit button) > >> > >> Emmanuel > >> > >> Karr, David a écrit : > >>> For better or worse, our Perforce projects use labels for > >> versioning, > >>> instead of branches (or anything else). If Continuum > will work for > >>> me, I'll need to create a handful of projects for the same > >>> application, for different versions. Each one will specify a > >>> different label to pull from SCM. I don't see a way to > do this in > >>> Continuum. I was able to get this to work with > >> CruiseControl, but I'd > >>> prefer to move to Continuum if it will work. > >>> > >>> > >>> > >> > > > > > > > >
