Skip to content

A new line in the comment text seems to cause non-match #93

@efip-ns

Description

@efip-ns

Jenkins and plugins versions report

Environment
Same as #91 

What Operating System are you using (both controller, and any agents involved in the problem)?

Linux

Reproduction steps

  1. Step 1: define the triggering comment as \\[ci-merge\\]
  2. Step 2: issue a comment of [ci-merge]\r\n (a new line in the end).

Expected Results

I'd expect the comment to trigger the build, as it says in the documentation:

Regular expression matching

The regex is not surrounded with any markers and uses the Pattern.CASE_INSENSITIVE and Pattern.DOTALL Java flags.

Actual Results

The build is not triggered.

Anything else?

The build is triggered after I edit the comment and remove the new line.

Are you interested in contributing a fix?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions