I have the SVN structure below:

/dir0/file1
/dir1/
/dir1/dirA/ (contains svn::externals of /dir0/file1)
/dir1/dirB/ (contains svn::externals of /dir0/file1@10)

The dir1/ above contains a sub-directory dirA/ with an external to file1 that lives at a separate directory, and a sub-directory dirB/ with an external to the same file but this time pinned to a revision.

I have a Jenkins job that checks out dir1/ and polls SVN for changes.

When I commit a change to file1, my Jenkins job is correctly triggered. However, it does not list my latest change.

More specifically,

When I check in a change to file1 at revision @14, my Jenkins job is triggered, and it lists the following changes:
file1@11
file1@12
file1@13

When I check in another change to file1 at revision @15 this time, my Jenkins job is triggered, and it lists the following changes:
file1@11
file1@12
file1@13
file1@14

In the above example, there are 2 issues:

• My latest change is not included in the Changes list
• All the changes that are greater to the revision of the pinned external are repeated in the Changes list

My expectation would be to get the first time just the revision @14:
file1 at revision @14
And the second to get just the revision @15 in the Changes list:
file1 at revision @15

It looks like the pinned external somehow overrides the latest known revision of the external.

I tried to find similar issues, and I believe that this issue may be relevant to the following two old issues:
JENKINS-2344
JENKINS-16533

I would appreciate any help or workaround.