A recent JIRA upgrade appears to have broken a Subversion post-commit hook that I have had in place for a number of years. This hook was working in tandem with the Commit Acceptance plugin (v1.6.0). The python script was using xmlrpc (
http://[base]/jira/rpc/xmlrpc) in the URL being called here:
# invoke JIRA web service
xmlrpcUrl = jiraBaseURL + 'jira/rpc/xmlrpc'
s = xmlrpclib.ServerProxy(xmlrpcUrl)
acceptance, comment = s.commitacc.acceptCommit(jiraLogin, jiraPassword, author, projectKey, message).split('|');
acceptance, comment = ['false', 'Unable to connect to the JIRA server at "' + xmlrpcUrl + '".']
I noted in the JIRA upgrade documentation that the use of rpc/xmlrpc is to be deprecated, though I assume that an update to the plugin would accommodate that.
In the meantime however, this hook is essential to our QA measures. How do I reinstantiate this functionality?
David, the Commit Policy Plugin is an alternative to the Commit Acceptance Plugin (with quite some major improvements).
One of the differences that it is using the REST API, so that it will work for 6.3 and especially for the JIRA 7 line (where the XMLRPC API is not just deprecated, but totally removed).
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot