-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for logical OR in plugins, i.e. one of these must succeed #76
Comments
One thought I had was perhaps a separate property which could have a condition specifying which plugins should (or shouldn't?) match. Something like this for the above case:
Then that would also solve the #58 issue I think, as the logging would be a lot clearer. Maybe a bit simpler might be adding something in the plugin string, like ! for disabling. | could be prefixed.
In this case CheckLog would always have to match, and either CheckJira1 or CheckJira2 |
Just realised that the initial config won't even work for us. It will check the key against both instances, so one will always fail. @gnustavo Do you see a solution? |
I've implemented the second/simpler proposal in #77. It would be appreciated if you could consider this. |
@gnustavo Any further thoughts on this? |
Within our company there are two Jira instances (merger/acquisition), and originally different teams used different instances, so we copied and renamed the CheckJira plugin for the second instance.
Now we're in the situation that for some projects multiple keys, from different instances should be allowed. We can probably solve that by using the CheckLog plugin, but the log messages become very unclear to users.
It would be nice if somehow multiple Jira instances could be supported with an option of requiring a valid jira key from one of the two.
The text was updated successfully, but these errors were encountered: