Configure::version(); will return the current version # of an official release or trunk version of the code. The branch code, which is where all changes are made, is not updated to return the correct version # until it has been merged to the trunk. -- /** * @author Larry E. Masters * @var string $userName * @param string $realName * @returns string aka PhpNut * @access public */
On Sun, Jun 8, 2008 at 11:37 PM, Grant Cox <[EMAIL PROTECTED]> wrote: > > I have the major and minor numbers hardcoded in my application > configuration file, and the actual revision appended using AD7Six's > snippet > > http://bakery.cakephp.org/articles/view/using-your-application-svn-revision-number > > > On Jun 9, 5:22 am, Ken <[EMAIL PROTECTED]> wrote: > > Like a good developer I want to set up a continuous integration > > process for my cake app. I can make ant work for me, but what do > > people recommend as far as tagging each deployment with a build #? I > > would like to use a scheme like: > > > > 1.00.bbb.p (where bbb is build and p is patch) > > > > ...and I would like my build/deployment process to label the build in > > SVN and then somehow get the version/build # onto the default layout. > > > > Thoughts? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
