I have a job that polls SVN and its SVN URL contains a pinned revision number. Now I understand that this is a silly configuration as why would you want to poll SVN for changes if you had specifically linked a job to a particular revision in SVN, however it is possible to setup and can cause jenkins issues with the job constantly running over and over.

To replicate, just create a job that points to SVN with its revision number specified, e.g...

http://mysvnserver/svn/mycode/trunk@101

With polling setup, every time the job runs it will detect that there is a change in SVN (if there have been changes post the revision specified) because the revision stored in the job doesn't match the latest revision for the repository linked.

To get around the issue, you run the job once and then disable it so that polling no longer occurs.

I believe the resolution to the issue should be that the SVN plugin should store back the pinned revision number to the job configuration for the polling checking, if the job specifies a specific revision in the SVN URL.