From: Julian S. <sim...@gm...> - 2010-10-28 13:58:18
|
Hi, On 19 October 2010 17:54, Paul Coste <pau...@gm...> wrote: > Thanks Julian. Sounds pretty straightforward. Some additional questions: > > > - What would be the best way of getting the CruiseControl official > version and other information from within the code, so that I can plug it > into the client name? > > There's a property in the build called 'cc.version' that should be available at release time. > > - Are there any guidelines about what versions of StarTeam should be > supported by CruiseControl? Can we safely part ways with versions that have > reached end of life from a vendor support perspective? My thoughts: the > next version of StarTeam Server will not support clients older than 2005 R2 > (i.e. version 8.0); 2005 R2 itself is no longer supported, and 2006 is on > its way out. I would say that supporting it back to version 2006 would be > preferable, but 2005 R2 might be possible. > > I'd go with that. :) Best J. > > > Thanks, > Paul > > > On Tue, Oct 19, 2010 at 6:17 AM, Julian Simpson <sim...@gm...>wrote: > >> Hi Paul, >> >> This kind of thing seems pretty standard. You can submit patches for >> documentation, or code. >> >> http://cruisecontrol.sourceforge.net/contributions.html >> >> <http://cruisecontrol.sourceforge.net/contributions.html>Having used >> CruiseControl and StarTeam, it would be nice to lay some ghosts to rest! >> >> Julian. >> >> On 18 October 2010 03:51, Paul Coste <pau...@gm...> wrote: >> >>> Hello, >>> >>> I am a StarTeam expert of over 12 years, and an experienced Java >>> developer, and would like to propose some enhancements to your StarTeam >>> plugin. I am not sure the best way to go about this, but I would appreciate >>> the opportunity to post code changes to the community. The following is the >>> list of proposed changes: >>> >>> 1) Add the code ClientApplication.setName("CruiseControlPlugin >>> <version.number>") during initialization of the plugin. This will cause >>> this string to be the client identifier in the StarTeam application log >>> file. Otherwise the plugin shows as "Unknown Application." This is very >>> important from a standardization and administration perspective when there >>> are many teams using StarTeam and we want to know who is using what kind of >>> plugin. This is also important in StarTeam 2009 and above, in order to >>> conform with the new client connection control feature, which can block >>> logins based on client name, SDK version, etc. (This particular function >>> call is supported all the way back to version 5.3, I believe, although I >>> don't know how far back you need to go anyway, since current support for >>> StarTeam only goes back to version 2006.) >>> >>> 2) I would like to address the documentation which states that the Jar >>> file is external and not freely available. This was true until several >>> months ago; now the new company Micro Focus (which bought Borland) has >>> released StarTeam Express edition which is free to up to 10 users, and for >>> which the SDK Jar file is included fully functional. This may actually put >>> the StarTeam plugin back into the standard library of plugins distributed as >>> binary, since the SourceForge team will be able to compile the library. >>> >>> 3) The documentation states that the StarTeam plugin is based on the >>> command-line interface. If this is true, the newest command-line interface >>> now supports encrypted (i.e. obfuscated) external password files, which is a >>> preferred way to operate, so that developers do not store clear text >>> passwords in their build scripts or properties files, allowing these files >>> to be safely stored in source control without compromising security. I >>> would like to add this as a new feature. >>> >>> Please let me know how I can contribute. For my company I plan on making >>> custom modifications, for item #1 and #3, but these should be included as a >>> general enhancement to the community if possible. >>> >>> Thank You, >>> Paul Coste >>> >>> >>> ------------------------------------------------------------------------------ >>> Download new Adobe(R) Flash(R) Builder(TM) 4 >>> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >>> Flex(R) Builder(TM)) enable the development of rich applications that run >>> across multiple browsers and platforms. Download your free trials today! >>> http://p.sf.net/sfu/adobe-dev2dev >>> _______________________________________________ >>> Cruisecontrol-devel mailing list >>> Cru...@li... >>> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel >>> >>> >> >> >> -- >> Julian Simpson >> The Build Doctor Ltd. >> http://www.build-doctor.com >> ju...@bu... >> (+44) 207 183 0323 >> >> >> >> ------------------------------------------------------------------------------ >> Download new Adobe(R) Flash(R) Builder(TM) 4 >> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >> Flex(R) Builder(TM)) enable the development of rich applications that run >> across multiple browsers and platforms. Download your free trials today! >> http://p.sf.net/sfu/adobe-dev2dev >> _______________________________________________ >> Cruisecontrol-devel mailing list >> Cru...@li... >> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel >> >> > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Cruisecontrol-devel mailing list > Cru...@li... > https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel > > -- Julian Simpson The Build Doctor Ltd. http://www.build-doctor.com ju...@bu... (+44) 207 183 0323 |