|
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. Key: JENKINS-14000 URL: https://issues.jenkins-ci.org/browse/JENKINS-14000 Project: Jenkins Issue Type: New Feature Components: email-ext Affects Versions: current Reporter: Steve Rowe Assignee: Slide-O-Mix Priority: Minor Fix For: current Content token BUILD_LOG_REGEX matches the given regex against each line of the build log. I propose to add a new content token BUILD_LOG_MULTILINE_REGEX, just like BUILD_LOG_REGEX, but with two modifications: # Matches are against the full content of the build log, rather than line-at-a-time. As a result, the regex can recognize multiple log lines in a single match, either by direct specification, or using the DOTALL modifier, e.g. {{(?s:.*)}}. # No context arguments ({{linesBefore}} and {{linesAfter}}) - if the user wants this behavior, their regex can do the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/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/email-ext-plugin/pull/40 > 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. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JENKINS-14000 > URL: https://issues.jenkins-ci.org/browse/JENKINS-14000 > Project: Jenkins > Issue Type: New Feature > Components: email-ext > Affects Versions: current > Reporter: Steve Rowe > Assignee: Slide-O-Mix > Priority: Minor > Fix For: current > > > Content token BUILD_LOG_REGEX matches the given regex against each line of the build log. > I propose to add a new content token BUILD_LOG_MULTILINE_REGEX, just like BUILD_LOG_REGEX, but with two modifications: > # Matches are against the full content of the build log, rather than line-at-a-time. As a result, the regex can recognize multiple log lines in a single match, either by direct specification, or using the DOTALL modifier, e.g. {{(?s:.*)}}. > # No context arguments ({{linesBefore}} and {{linesAfter}}) - if the user wants this behavior, their regex can do the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
| Powered by Nabble | Edit this page |

Fixed in 2.22