|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
There are IMO 2 different topics here:
I) you get an error in the subversion-plugin. You assume that this comes from the timestamp handling of the plugin. I'm not convinced that's the problem. What you can do:
a) ask for help on the users list
b) patch the subversion-plugin according to your suggestions and confirm that that's really your problem
II) you criticize the handling of timestamps in the svn-plugin.
I've not initially developed the plugin, so I cannot provide any detailed explanations, why the timestamp-approach was chosen. But I know that using timestamps has certain advantages (e.g. if you use multiple repositories / job or when using matrix jobs).
What you can do:
a) search for the existing issues in JIRA and add any new insights, if you have them
b) provide a Github pull request with the changes from I) b)