Hi, All. As we discussed in last night's meeting, there is a new Git Integration Plugin <https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=server&tab=overview> installed on issues.gpii.net. This appears to have been installed and set up to support work with the gpii-infra repositories.
As opposed to the built-in developer tools integration <https://confluence.atlassian.com/adminjiraserver073/integrating-with-development-tools-867028207.html>, the plugin supports a wider range of services (including GitLab) and higher visibility of activity on connected repositories (more than just a summary on the right side of the issue screen). There was some question about the new "issue link types". In looking through all of the issues that appear to use the plugin <https://issues.gpii.net/issues/?jql=project%3DGPII%20and%20gitCommitsReferenced%20is%20not%20empty%20order%20by%20updated%20DESC%20>, it doesn't appear to me that it's used. It seems like we should be able to safely remove it. I am happy to try that. However, there are some things we should discuss. The key plugin features can be scoped to particular projects, but as most of us work in the shared GPII project, this is not much help. At the moment, we have two layers of GitHub integration, one of which is not fully configured for the range of projects we support, and this can lead to some confusion. As an example, the recent issue GPII-2973 <https://issues.gpii.net/browse/GPII-2973> has commits in an associated gpii-infra repository, and you can see the new "Git Source Code" module on the right has information. You can also see information in the new "Git Rollup" and "Git Commits" tabs. Now look at GPII-2564 <https://issues.gpii.net/browse/GPII-2564>, which is an issue that demonstrates the Developer Tools integration. It has a separate "Development" module on the right side of the issue, which shows recent activity and the fact that a pull request exists. Since the rest of our repositories are not yet configured in the new plugin, the new plugin incorrectly suggests that there is no Git activity related to this issue in all three of its modules. I would propose that we review the new plugin's features in next week's architecture meeting and discuss how best to resolve this, for example by setting up both kinds of integration for our repositories. Cheers, Tony
_______________________________________________ Architecture mailing list [email protected] https://lists.gpii.net/mailman/listinfo/architecture
