Quantcast

[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 content of the build log.

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[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 content of the build log.

JIRA noreply@jenkins-ci.org
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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[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 content of the build log.

JIRA noreply@jenkins-ci.org

    [ 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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[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 content of the build log.

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Slide-O-Mix resolved New Feature JENKINS-14000 as Fixed

Fixed in 2.22

Change By: Slide-O-Mix (16/Jun/12 6:14 AM)
Status: Open Resolved
Fix Version/s: current
Resolution: Fixed
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[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 content of the build log.

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Loading...