[Anthill-pro] SVN Label Source
Mathew Joseph
mjoseph at bravurasolutions.com
Wed Sep 12 14:38:04 CDT 2007
No particular reason, I was wondering what the difference was. Now i
know. In any case, for the labelling of the source, it is mentioned that
i can use a script. Can you tell me what I can use to label the tag
with the current stamp of the build.
Mathew
On Wed, 2007-09-12 at 11:35 -0600, Eric Minick wrote:
> Mathew,
>
> I don't think you need to use the same folder. You should be able to use
> the Subversion Remote Label command to apply a new label to the code as
> it was. Is there a reason a remote label wouldn't work?
>
> -- Eric
>
> Mathew Joseph wrote:
> > Hi Everyone,
> > I am not getting the label source step correct.
> > My current source configuration is say
> >
> > source url
> > <project>/trunk
> >
> > tags url
> > <project>/tags
> >
> > I want the source to be labelled as
> >
> > <project>/tags/<stamping strategy>
> >
> >
> > I have 2 workflows. The first one builds and the second one releases the
> > build
> >
> > To ensure that the release workflow works, it has to use the same
> > working directory as the previous one since the SVN copy has to use the
> > folder to which the code was checkedout.
> >
> > how do i ensure that the populate workspace (SVN specific) step in the
> > first workflow uses a specific working directory, as opposed to the
> > workflow name..
> >
> > thanks,
> > Mathew
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> >
> >
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
--
Regards,
Mathew Joseph
Build & Release Engineer
Bravura Solutions
More information about the Anthill-pro
mailing list