-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Debian 6, Tomcat 6, Jenkins 1.500, Subversion
I want Jenkins to check SVN every few minutes for changes. So I give a URL to check: svn://host/some/path/project/trunk. Jenkins says, I am not authenticated. So I follow the link to authenticate. As I want to authenticate only once for all projects, I provide the URL svn://host, not the complete path to one particular project. I give user and password, and Jenkins says the authentication is OK.
When I come back to the job config, Jenkins still warns that the authentication is not working. I ignore this and start a build, and look, Jenkins can access the SVN repository without problems. So I go back to the config, and still Jenkins says, it cannot authenticate... weird.
The funny thing is that at some later time when I check again the config, the warning is gone.
Tried it several times, always with the same behaviour: The warning will stay there for rather long time, then suddenly is gone.
Browser is IE9.