That's agreed. But it doesn't mean that Jenkins should be picking up "current revision" for the build env. variable and show "last changed" on the build page.
On Jun 6, 5:09 am, <matthew.web...@diamond.ac.uk> wrote: > I think this is a consequence of the way subversion works. > > A subversion checkout of part of the repo (eg trunk/) has two revision > numbers associated with it - the "current revision" number for the item > (directory, file, whatever), and the "last changed" revision number. You can > see these by using "svn info <dir>". The "revision number" for the repo > advances whenever anything is checked in to any part of the repository. > > Matthew > > > > > > > > > > > -----Original Message----- > > From: jenkinsci-users@googlegroups.com > > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of pmon > > Sent: 04 June 2012 07:46 > > To: Jenkins Users > > Subject: SVN revision number inconsistency between build page and > > environment variable > > > Hi > > > I have an annoying problem, I would be happy to get ideas about how to > > solve it. > > > I have an SVN repository, let's sayhttp://myserver/myrepo > > > For my job, I check out the source from this > > repo:http://myserver/myrepo/trunk > > > Let's say, that between two builds two revisions has been created in > > the repository x and x+1. The first is a result of a change in > >http://myserver/myrepo/trunk, the second is the results of change in > >http://myserver/myrepo/branches. > > > What will happen after the new build is that the build page will show > > the last changed revision under the checkout URL (in this case > >http://myserver/myrepo/trunk) which is "x", and the build log will > > show "At revision x+1" and the environment variable SVN_REVISION which > > I'm using in the version string of the target build is also set to "x > > +1". > > > This is confusing. Do you have an idea how to have the checkout > > revision to appear on the build page? > > > Thanks a lot > > PMon > > -- > This e-mail and any attachments may contain confidential, copyright and or > privileged material, and are for the use of the intended addressee only. If > you are not the intended addressee or an authorised recipient of the > addressee please notify us of receipt by returning the e-mail and do not use, > copy, retain, distribute or disclose the information in or attached to the > e-mail. > Any opinions expressed within this e-mail are those of the individual and not > necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any > attachments are free from viruses and we cannot accept liability for any > damage which you may sustain as a result of software viruses which may be > transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in England and > Wales with its registered office at Diamond House, Harwell Science and > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom