[bugfix] Fix Github Branch Commit Checks Bug

[smilejj91]

This is a PR fixing an issue related to Commit Check in the Github Branch section of the build trigger.

1. Fixed an issue where the job configuration was broken when saving after activating the Commit Message pattern option.

• The issue is related to this link

2. Fixed an issue where the job was not triggered even if it matched the Commit Message Pattern.

We would appreciate your positive review.

Thank you.

---

This change is 

[smilejj91]

@KostyaSha Hello. I mentioned you because I know you are the maintainer of the repository. I would appreciate it if you could check the PR. Thank you. 😀

[KostyaSha]

would be good to make some test...

[smilejj91]

would be good to make some test...

@KostyaSha you're right. I have already checked the relevant functional tests and provided a PR. Is it possible to attach a test image for confirmation?

[smilejj91]

[how to reproduce issue]
Create Freestyle Job -> Job Configuration -> Build triggers -> Github Branches -> Trigger Events -> Commit Checks -> Commit Message Pattern -> Job Save -> Reopen Job Configuration

[before apply this commit] : job configuration is broken

[after apply this commit] : job configuration is not broken

[smilejj91]

I already apply this commit and use github branches commit check feature. I am using it well without any issues so far.
If this commit is reflected in the official plugin, it would be nice for me to not have to separately manage the custom plugin.

[KostyaSha]

I mean for GitHubBranchCommitMessageCheck.java not, UI.

[smilejj91]

I mean for GitHubBranchCommitMessageCheck.java not, UI.

@KostyaSha Oh, I see. It would be a good idea to test it in your own environment before and after applying the commit. It seems difficult to show the functional test results before and after modification in this PR.

What is certain is that if the current commit is not reflected, the commit message is compared well, but when it passes after comparison, the job is not triggered.

[KostyaSha]

Usually it's done with mocks, you initialise only MessageCheck and pass mocked objects that contains commit pattern and check that it return expected cause

[smilejj91]

@KostyaSha thank you. Test execution may have been skipped in the master branch, so I thought the test had passed. Related test code was modified and reflected in additional commits.
test-success.txt

[smilejj91]

@KostyaSha Hello. :) Two weeks have passed since the test was performed and the normal results were attached. Is there anything additional that needs to be checked for the PR to be reflected? Or is the related commit still under review?

[smilejj91]

@kvanzuijlen Can you check the PR? I feel like KostyaSha can't confirm.

[KostyaSha]

sorry, too busy atm, we look as soon as find free time