[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Title: Message Title Robin Pradel commented on JENKINS-26458 Re: org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy Got the same problem but the hint from Madrikeka Changing the SVN version from 1.7 to 1.8 in the Jenkins configuration fixed this issue for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Title: Message Title
Robin Pradel edited a comment on JENKINS-26458
Re: org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Gotthesameproblembutthehintfrom[~ madrikeka pon ]{quote}ChangingtheSVNversionfrom1.7to1.8intheJenkinsconfiguration{quote}fixedthisissueforme.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Title: Message Title Robin Pradel commented on JENKINS-26458 Re: org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy Maybe I should better explain my way to this ticket, because it was a bit different than the ticket creator described. I updated Jenkins (1.594 - 1.609.1 LTS) and also several plugins (subversion: 2.4.5 - 2.5.1) and then the issue came up. Hope this helps for reproducing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26458) E155021: This client is too old to work with the working copy
Title: Message Title Robin Pradel commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Sorry, I wrote and post my comment while you already updated the status. It seems likely to be the same svn cli issue for me like you described above. Our build server has this tool installed and I can't exclude that somebody else did sth with it. Thanks for your time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Robin Pradel
created JENKINS-14508
Default pre-send script in Jenkins Configuration
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
19/Jul/12 6:07 PM
Description:
It would be very nice, if there is also an input field for a default pre-send script like the default email content and recipients which is triggered if the according placeholder (e.g. ${DEFAULT_PRE-SEND_SCRIPT}) is present in the project configuration.
Project:
Jenkins
Priority:
Major
Reporter:
Robin Pradel
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
[JIRA] (JENKINS-14484) Define time period in which a mail is desired
Robin Pradel created JENKINS-14484 Define time period in which a mail is desired Issue Type: Improvement Affects Versions: current Assignee: Slide-O-Mix Components: email-ext Created: 18/Jul/12 1:29 PM Description: We build every night our projects for testing issues. Also the system should provide on the same way the latest development state to all developers. When a quick fix rises or extra test runs are manually triggered, it would be nice to disable email notification because the user triggering this build will observe or check it by browser. In general these actions take place during the day, so a rule like: "send email on error only for builds between 21:00 - 06:00" would be very nice. Project: Jenkins Priority: Major Reporter: Robin Pradel 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
