[JIRA] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build

Tue, 09 Apr 2013 13:20:38 -0700

kutzi commented on Bug JENKINS-17431

Okay the 2nd paragraph is no big deal - it just says that the time defaults to 0 hour if you don't specify it.
About the 1st paragraph: so what is the point you want to make? That if you really want to mess with the timestamp, you can.
Yeah okay, you may, but I don't think that's something 'sane' to do.

Let me tell you how I see it:

  • Jenkins has been using timestamps in the svn-plugin for a very long time. This has worked well for the big majority of users. There's an occasional bug report about 'wrong updates' which almost always has something to do with out-of-sync clocks and so easily resolved.
  • for some reason it is not working for you. Maybe because you messed with the timestamps. That's IMO a problem with your configuration and no bug in the svn-plugin
  • if you have a better idea on how to handle updates in the svn-plugin, feel free to post your concrete idea (loose ideas to work with revisions instead of timestamps have already been posted before. They're IMHO no big help) - i.e. as a Github pull request. However, I think that the danger of introducing backwards incompatible changes by this is IMO very very big. So we would need to introduce it as an optional setting. Which would in turn bring up the question why we need this setting, when the plugin is working very well in the vast majority of environments ...

BTW: you may also want to experiment with the @HEAD setting in the repository URLs
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.
 
 

Reply via email to