[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577

2014-08-22 Thread sar...@syr.edu (JIRA)
Steve Rowe c

[JIRA] (JENKINS-14132) Very long content token string parameter triggers a StackOverflowError

2012-06-19 Thread sar...@syr.edu (JIRA)
Steve Rowe c

[JIRA] (JENKINS-14132) Very long content token string parameter triggers a StackOverflowError

2012-06-18 Thread sar...@syr.edu (JIRA)
Steve Rowe c

[JIRA] (JENKINS-14132) Very long content token string parameter triggers a StackOverflowError

2012-06-18 Thread sar...@syr.edu (JIRA)
Steve Rowe c

[JIRA] (JENKINS-14132) Very long content token string parameter triggers a StackOverflowError

2012-06-18 Thread sar...@syr.edu (JIRA)
Steve Rowe c

[JIRA] (JENKINS-14132) Very long content token string parameter triggers a StackOverflowError

2012-06-18 Thread sar...@syr.edu (JIRA)
Steve Row

[JIRA] (JENKINS-14000) Add new content token BUILD_LOG_MULTILINE_REGEX, which allows regexes to match line terminators in build logs (in addition to all other characters), by matching against the full

2012-06-16 Thread sar...@syr.edu (JIRA)
Steve Rowe c

[JIRA] (JENKINS-14000) Add new content token BUILD_LOG_MULTILINE_REGEX, which allows regexes to match line terminators in build logs (in addition to all other characters), by matching against the full

2012-06-02 Thread sar...@syr.edu (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163450#comment-163450 ] Steve Rowe commented on JENKINS-14000: -- See pull request https://github.com/jenkinsci/e

[JIRA] (JENKINS-14000) Add new content token BUILD_LOG_MULTILINE_REGEX, which allows regexes to match line terminators in build logs (in addition to all other characters), by matching against the full

2012-06-02 Thread sar...@syr.edu (JIRA)
Steve Rowe created JENKINS-14000: Summary: Add new content token BUILD_LOG_MULTILINE_REGEX, which allows regexes to match line terminators in build logs (in addition to all other characters), by matching against the full content of the build log.

[JIRA] (JENKINS-13976) Allow backslash-escaped line terminators in content token string arguments

2012-06-01 Thread sar...@syr.edu (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163430#comment-163430 ] Steve Rowe commented on JENKINS-13976: -- Thanks! > Allow backslash-esca

[JIRA] (JENKINS-13976) Allow backslash-escaped line terminators in content token string arguments

2012-05-31 Thread sar...@syr.edu (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated JENKINS-13976: - Summary: Allow backslash-escaped line terminators in content token string arguments (was: Allo

[JIRA] (JENKINS-13976) Allow content token arguments to contain line terminators

2012-05-31 Thread sar...@syr.edu (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163393#comment-163393 ] Steve Rowe commented on JENKINS-13976: -- Done: https://github.com/jenkinsci/email-ext-pl

[JIRA] (JENKINS-13976) Allow content token arguments to contain line terminators

2012-05-31 Thread sar...@syr.edu (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163387#comment-163387 ] Steve Rowe commented on JENKINS-13976: -- Okay, will do. > Allow content

[JIRA] (JENKINS-13976) Allow content token arguments to contain line terminators

2012-05-31 Thread sar...@syr.edu (JIRA)
Steve Rowe created JENKINS-13976: Summary: Allow content token arguments to contain line terminators Key: JENKINS-13976 URL: https://issues.jenkins-ci.org/browse/JENKINS-13976 Project: Jenkins