Hiya, what does the svn info say from command in detail? I assume that the different revisions can be explained quite easy. Rev 23205 is probably the actual revision. That continues counting up each time something also adjacent (same repository/branch/project) is commited even though nothing has been changed in the file in question! "the last changed revision is *23198*" is reflecting the - as it already says - last change in that specific file.
Don't mix these to revisions up ;) 23205 may be of exact same content as 23198. If you then change the specific file should all revision numbers you have mentioned count up to 23206. That would also explain why the revision sometimes stays for days on the same number. ;) Take care Jan On 4 Apr., 09:42, Blaž Križaj <blaz.kri...@gmail.com> wrote: > Having exactly the same issue. Looking into it, maybe just use svn command? > In my case I only need current(latest) revision when project starts > building so it creates dir named with revision and date. > SVN command would be something like: svn info |grep Revision: |cut > -c11-(Where you need to be in working dir). > > Regards, > Blaž > > > > > > > > On Tuesday, 15 November 2011 02:27:00 UTC+1, Ingo Richter wrote: > > > Hi, > > > I have a Jenkins setup that uses the subversion plugin to determine > > changes to my repository. To my surprise, I noticed today that the > > SVN_REVISION environment variable doesn't have the latest revision assigned. > > In my case it always lags behind a couple of revisions and it sticks there > > for a couple of days now. > > > I made the observation, that the correct revision was determined by the > > subversion plugin (as seen in the build log): > > > ------>8-------------------- > > > Started by timer*18:00:25* Updating https:// > > <https://opensource.adobe.com/svn/opensource/private/flex/sdk/branches...>myrepo/projectA*18:00:41* > > At revision *23205* > > > ------>8-------------------- > > > The same revision is determined by my build script that gets called to > > build the product. > > > If I look at the output of *svn info,* it tells me that the revision is > > *23205* (the same as in the build log) and that the last changed revision > > is *23198*. This is the value that SVN_REVISION has. > > > Has anyone seen this in their setup? How does the subversion plugin > > determine the value for SVN_REVISION? The value doesn't seem to be current > > revision. > > > My current Jenkins setup looks like: > > > Jenkins v1.437 > > javadoc v1.0 -http://wiki.jenkins-ci.org/display/JENKINS/Javadoc+Plugin > > ant v1.1 -http://wiki.jenkins-ci.org/display/JENKINS/Ant+Plugin > > Token Macro Plugin v1.4 > > -http://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin > > Maven Integration plugin v1.437 > > -http://wiki.jenkins-ci.org/display/JENKINS/Maven+2+Project+Plugin > > Static Analysis Utilities v1.32 -http://wiki.jenkins-ci.org/x/CwDgAQ > > AnsiColor v0.1.2 > > -http://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin > > Backup plugin v1.6.1 > > -http://wiki.jenkins-ci.org/display/JENKINS/Backup+Plugin > > build-name-setter v1.3 > > -http://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin > > Build Pipeline Plugin v1.2.3 > > -https://code.google.com/p/build-pipeline-plugin > > Jenkins build timeout plugin v1.8 > > -http://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin > > Jenkins CVS Plug-in v1.6 > > -http://wiki.jenkins-ci.org/display/JENKINS/CVS+Plugin > > Jenkins Continuous Integration game v1.18 > > -http://wiki.jenkins-ci.org/display/JENKINS/The+Continuous+Integration... > > Hudson Collapsing Console Sections Plugin v1.3 > > -http://wiki.hudson-ci.org/display/HUDSON/Collapsing+Console+Sections+... > > Console Column Plugin v1.5 > > -http://wiki.jenkins-ci.org/display/JENKINS/Console+Column+Plugin > > Jenkins Subversion Plug-in v1.34 > > -http://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin > > Dump Info BuildWrapper Plugin v1.1 > > -http://wiki.hudson-ci.org/display/HUDSON/DumpInfo+BuildWrapper+Plugin > > Jenkins Email Extension Plugin v2.15 > > -http://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin > > emotional-jenkins-plugin v1.1 > > -https://wiki.jenkins-ci.org/display/JENKINS/Emotional+Jenkins+Plugin > > Hudson FlashLog Plugin v1.0 > > -http://wiki.hudson-ci.org/display/HUDSON/FlashLog+Plugin > > Groovy Postbuild v1.4 > > -http://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin > > Jenkins instant-messaging plugin v1.20 > > -http://wiki.jenkins-ci.org/display/JENKINS/Instant+Messaging+Plugin > > Jenkins Jabber notifier plugin v1.21 > > -http://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin > > Rebuilder v1.9 -http://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin > > Jenkins SSH Slaves plugin v0.21 > > -http://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin > > Timestamper v1.2.2 -http://wiki.jenkins-ci.org/display/JENKINS/Timestamper > > Jenkins Translation Assistance plugin v1.8 > > -http://wiki.jenkins-ci.org/display/JENKINS/Translation+Assistance+Plugin > > > Is there anything that does easily explain this behavior? > > Thanks you, > > Ingo