[Anthill-pro] How to tie SVN Revision to Stamp/Build Number

Tue Jan 6 07:33:19 CST 2009

Look in the documentation on using the changeset feature with SVN,
that's how it gets into the stamp. Did my screen shots ever get approved
by the moderator, those showed it explicitly.

==========
Curtis Yanko
Application & Developer Infrastructure Services
Source->Build->Deploy
W: 860.702.9059
M: 860.881.2050

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of
Gurinder.Randhawa at tu-group.com
Sent: Monday, January 05, 2009 5:44 PM
To: AnthillPro user and support list.
Subject: [Anthill-pro] How to tie SVN Revision to Stamp/Build Number

We are moving over from CVS world to Subversion and would like to use
SVN revision number as build number. 

How can we set this up in AnthillPro, is there any documentation on
setting this up, also what is best practice with SVN? I got some info on
this from Yanko a few weeks back passing in lateststampvalue into
manifest built number property, however didn't see how SVN revision is
retrieved. 

--Gurinder 

From: 	"Yanko, Curtis" <curt_yanko at uhc.com> 
To: 	"AnthillPro user and support list."
<anthill-pro at lists.urbancode.com> 
Date: 	23/12/2008 11:21 AM 
Subject: 	RE: [Anthill-pro] Using parent buildNumber property in
dependencies

________________________________

Then we pass to each builder so it can be included in the Manifest of
the Component: 

-Dbuild.number=${bsh:StampLookup.getLatestStampValue()} 
-Dbuild.time="${property:workspace.date}"
-Dsvn.url=${bsh:sourceConfig=BuildLifeLookup.getCurrent().getProfile().g
etSourceConfig();module=sourceConfig.getModuleArray();return
sourceConfig.getRepository().getSvnRoot() + "/" + module[0].getUrl()} 
Now, if I look at any given component in production, or anywhere, I can
see what version it is, when it was built and where it came from. Since
the build number contains the SVN revision there is immediate
traceability straight to it without any further lookup. 
========== 
Curtis Yanko 
Application & Developer Infrastructure Services 
Source->Build->Deploy 
W: 860.702.9059 
M: 860.881.2050 

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com
<mailto:anthill-pro-bounces at lists.urbancode.com> ] On Behalf Of
Gurinder.Randhawa at tu-group.com
Sent: Saturday, February 07, 2009 1:34 PM
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Using parent buildNumber property in
dependencies

Yes we've just moved over from CVS to Subversion and would definetly
like to tie to the SVN revision number, could you outline 
steps involved in doing this or is there some documentation on this? 

Also can we show the SVN revision as a Stamp on AntHill dashboard?

Thanks 

_Gurinder

From: 	"Yanko, Curtis" <curt_yanko at uhc.com> 
To: 	"AnthillPro user and support list."
<anthill-pro at lists.urbancode.com> 
Date: 	23/12/2008 10:23 AM 
Subject: 	RE: [Anthill-pro] Using parent buildNumber property in
dependencies

________________________________

We version every component independently and tie that to SVN revision. 

In your scheme you will end up with identical components having
different identifiers over their life. 

========== 
Curtis Yanko 
Application & Developer Infrastructure Services 
Source->Build->Deploy 
W: 860.702.9059 
M: 860.881.2050 

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com
<mailto:anthill-pro-bounces at lists.urbancode.com> ] On Behalf Of
Gurinder.Randhawa at tu-group.com
Sent: Saturday, February 07, 2009 1:19 PM
To: anthill-pro at lists.urbancode.com
Subject: [Anthill-pro] Using parent buildNumber property in dependencies

How can i pass on my "buildNum" property from top level build to
dependent builds? 

I'd like to use the same build number across all my dependencies. Is
there a better way to do this? 

_Gurinder 

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
<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/20090106/fa832436/attachment-0001.htm