Comments on: Version Labeling and Continuous Frustration http://www.spiderstrategies.com/blog/index.php/2007/04/version-labeling-and-continuous-frustration/ Notes on Performance Management and writing the software behind it Thu, 02 Sep 2010 07:05:09 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Keith http://www.spiderstrategies.com/blog/index.php/2007/04/version-labeling-and-continuous-frustration/comment-page-1/#comment-1213 Keith Sun, 15 Apr 2007 16:29:52 +0000 http://www.spiderstrategies.com/blog/?p=37#comment-1213 First, I would have CI engines consider the build to start with its invocation of "ant" (or maven, bash script, etc). Starting with a project's update/checkout is absurd (how can you start a build with nothing to build?). Secondly, I would somehow enable properties defined by my build.xml to be easily passed-back to the CI's wrapper. Currently property definitions seem to be one way -- I can have a CI wrapper pass properties to my build, but I can't have my build pass properties back to the wrapper. That way, I could instruct the CI Engine to use my "${build.label}", generated during the course of my build, as the version label. First, I would have CI engines consider the build to start with its invocation of “ant” (or maven, bash script, etc). Starting with a project’s update/checkout is absurd (how can you start a build with nothing to build?).

Secondly, I would somehow enable properties defined by my build.xml to be easily passed-back to the CI’s wrapper. Currently property definitions seem to be one way — I can have a CI wrapper pass properties to my build, but I can’t have my build pass properties back to the wrapper. That way, I could instruct the CI Engine to use my “${build.label}”, generated during the course of my build, as the version label.

]]> By: Jason Yip http://www.spiderstrategies.com/blog/index.php/2007/04/version-labeling-and-continuous-frustration/comment-page-1/#comment-1193 Jason Yip Sat, 14 Apr 2007 00:25:57 +0000 http://www.spiderstrategies.com/blog/?p=37#comment-1193 Ideally, how would you want it to work? Ideally, how would you want it to work?

]]> By: links for 2007-04-12 | Urubatan`s Weblog http://www.spiderstrategies.com/blog/index.php/2007/04/version-labeling-and-continuous-frustration/comment-page-1/#comment-1168 links for 2007-04-12 | Urubatan`s Weblog Thu, 12 Apr 2007 10:28:34 +0000 http://www.spiderstrategies.com/blog/?p=37#comment-1168 [...] Version Labeling and Continuous Frustration [...] [...] Version Labeling and Continuous Frustration [...]

]]> By: AnonymousJavaProgrammer http://www.spiderstrategies.com/blog/index.php/2007/04/version-labeling-and-continuous-frustration/comment-page-1/#comment-1160 AnonymousJavaProgrammer Wed, 11 Apr 2007 16:49:16 +0000 http://www.spiderstrategies.com/blog/?p=37#comment-1160 I have a similar situation. I use the Ant buildnum task in my build.xml script. I want to checkout the HEAD, use buildnum to get a unique build number, and then use 'cvs tag' to tag the artifacts associated with my build. I have a similar situation. I use the Ant buildnum task in my build.xml script. I want to checkout the HEAD, use buildnum to get a unique build number, and then use ‘cvs tag’ to tag the artifacts associated with my build.

]]>