INFRA-250 Document civicrm-builder visibly
- Document the plugins that CiviCRM Builder runs
- Do this visibly, eg on https://github.com/civicrm-builder profile
- Give clear instructions for contacting owner / admin
- Allow users to identify what to expect from the bot
Use case here was a PR ([PR9933|https://github.com/civicrm/civicrm-core/pull/9933] that did not get linked to the relevant JIRA issue (CRM-20004). Joe asked why this might have not happened as expected. I'd been wondering whether it was due to placement of the relevant JIRA issue number in PR title vs commit message, or some other issue (eg JIRA being down recently).
When investigating I found that the details were scattered about the place, including in:
- INFRA-231 (upcoming features?)
- [CiviCRM forum post from 2014|https://forum.civicrm.org/index.php?topic=33608.0]
- [Plugin documentation|https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin]
I suspect there's more, eg https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin doesn't look like it does the legwork of updating JIRA-PR connection by updating both PR (first comment?) and JIRA (links added via https://issues.civicrm.org/jira/secure/ViewProfile.jspa?name=civicrm-builder account).