Control Freak: config option to tolerate if Jira is not accessible

[Dávid Csákvári]

Hi!

We have some Jira Policies enabled to catch typos of Jira issues in the commit messages. However, when our Jira instance is down for maintenance, developers can’t push their code:

remote: Control Freak: java.lang.RuntimeException: JQL request to JIRA failed: com.atlassian.sal.api.net.ResponseException: org.apache.http.conn.HttpHostConnectException: Connect to <JIRA> [<JIRA>] failed: Connection refused (Connection refused)
remote: java.lang.RuntimeException: JQL request to JIRA failed: com.atlassian.sal.api.net.ResponseException: org.apache.http.conn.HttpHostConnectException: Connect to <JIRA> [<JIRA>] failed: Connection refused (Connection refused)
remote:   at com.bitbooster.hook.JiraUtil.query(JiraUtil.java:116)
remote:   at com.bitbooster.hook.JiraUtil.query(JiraUtil.java:67)
remote:   at com.bitbooster.hook.ControlFreakHook.jiraPolicyCheck(ControlFreakHook.java:1359)
remote:   at com.bitbooster.hook.ControlFreakHook.validateChange(ControlFreakHook.java:831)
remote:   at com.bitbooster.hook.ControlFreakHook.processReceive(ControlFreakHook.java:380)
remote:   at com.bitbooster.hook.ControlFreakPreReceive.preUpdate(ControlFreakPreReceive.java:120)
remote:

Due to testing and integration, a Jira upgrade can take significant amount of time.

Please consider adding a checkbox to the “Jira Policy” section, to disable Jira policies in case when there’s a connection problem to Jira. (Essentially ignore exceptions that are related to Jira connection, and e.g. only log a warning in this case.)

We greatly value valid Jira identifiers in commit messages, but if possible we’d avoid blocking developers in such scenarios.

Thanks,
David

‌