[Anthill-pro] Labeling SVN

Fri Oct 5 07:30:57 CDT 2007

Steve,

Thanks again. I pieced most of that together in the interim but here is
my dillema now.

I like to put our BLD labeles into tags/builds to help with the signal
to noice ration in there.

Howver, if I now come back with a secondary workflow to Release the
artifact and I want to label SVN to reflect that I need to somehow
reference the label in tags/build to put a label in tags???

I define two different source configurations to help facilitate this but
perhaps I am trying to be too clever.

Seems like the Remote Label Step can replace an exisiting label but I am
also guessing that the different offset isn't mking this easy.

So I now have ${bsh:StampLookup.getLatestStampValue()} as my label
string and ${bsh:StampLookup.getLatestStampValueForStyle("DEV")} as the
labelto replace. I'm thinking that this second might be a problem is
another build has accorred or is it scoped to this build life?? Also I'm
guessing that since that label exist in a different tags path than the
source config I'm using it wnt find it at all.

Ideas? Can I stick to using tags/builds and somehow accuretely reference
when the build occured in order to apply a REL tag later or should I
scrap the idea and keep it simple? Do my little scripts seem right or
will I get a DEV stamp from a different build life?

===
-Curt
W: 860.702.9059
M: 860.881.2050

________________________________

From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Steve
Boone
Sent: Thursday, October 04, 2007 10:50 AM
To: AnthillPro user and support list.
Cc: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Labeling SVN

Curtis,

Obtaining the latest stamp can be done with the helpers.  It would look
like this.

BuildLife bl = BuildLifeLookup.getCurrent();
String stamp = bl.getLatestStampValue();

The Remote Label step is generally used to apply a label (to a revision)
without having to actually check out the code.  A normal Label Step,
labels the code that is being checked out.  The Remote Label Step makes
it easier for the user to do a label at different stages of the build,
for example you could label your source "Released" after it passes the
appropriate testing environment.  

Hopefully this clears things up, let me know if you have any more
questions.

Regards,
Steve Boone

On 10/4/07, Yanko, Curtis <curt_yanko at uhc.com> wrote: 

	One more thing, I am getting confused between Label Source and
Remote Label Step.

	I also seem to have lost (again the stupid email migration) the
little script to pass in teh Stamp as a label.

	I want to apply the stamp as a label near the end of my
Originating workflow.

	===
	-Curt
	W: 860.702.9059
	M: 860.881.2050

________________________________

	From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Steve
Boone
	Sent: Thursday, October 04, 2007 9:56 AM
	To: AnthillPro user and support list.
	Subject: Re: [Anthill-pro] Codestation:publish Ant task problem
writingmetadata file

	Christopher,

	One of our developers was able to recreate this.  Deleting the
file fixes it. We are currently trying to determine what exactly causes
the issue.  

	Thank you for the information, 
	Steve Boone

	On 10/3/07, Christopher Power <chrispower36 at gmail.com> wrote: 

		I am trying to use the codestation:publish Ant task to
publish an artifact set to the local repository.  When I run the command
it successfully publishes the artifact locally, however it fails to
write the artifact.metadata file to the user's .codestation directory.  

		The following is the output...

		[codestation:publish] Retrieving Details For
Project-->Workflow >From http://server
		[codestation:publish]     Successfully published
artifacts for Project : Library to local repository 
		[codestation:publish] Warning:  Could not write
artifact.metadata file: C:\...user...\.codestation
\repo\21\artifact.metadata (Access is denied)
		[codestation:publish] Finished publishing artifacts to
local repository 

		I am not sure why access would be denied to that
particular directory...

		Thanks,
		Chris

		_______________________________________________
		Anthill-pro mailing list
		Anthill-pro at lists.urbancode.com 
		http://lists.urbancode.com/mailman/listinfo/anthill-pro

	This e-mail, including attachments, may include confidential
and/or 
	proprietary information, and may be used only by the person or
entity to 
	which it is addressed. If the reader of this e-mail is not the
intended 
	recipient or his or her authorized agent, the reader is hereby
notified 
	that any dissemination, distribution or copying of this e-mail
is 
	prohibited. If you have received this e-mail in error, please
notify the 
	sender by replying to this message and delete this e-mail
immediately.

	_______________________________________________
	Anthill-pro mailing list
	Anthill-pro at lists.urbancode.com 
	http://lists.urbancode.com/mailman/listinfo/anthill-pro

This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20071005/14697606/attachment-0001.htm