Jenkins Checkstyles: Explore the Viability of GitHub Integration

[JackEAllen]

As a: developer I would like Checkstyles to stop increasing and begin reducing in size through means of a stricter review process by integrating existing checkstyle static code analysis performed by Jenkins into GitHub as an on push action.

By doing this, checks will be displayed in GitHub for each branch and easier to include as part of a review when a PR has been created to merge into production. It is then up to the reviewers discretion to let branches be merged in if time critical if checkstyles increase, and to otherwise ask for a rework to resolve, passing only if the checkstyles remain the same or decrease in quantity.

In response to a discussion taken place in the retrospective Retrospective notes 2022.09.07, the purpose of this issue is to explore the viability of making this possible and creating an issue to make this possible if easily viable.

Acceptance Criteria

What is the acceptance criteria?

• Viability of integrating checkstyle code analysis through Jenkins into GitHub on push has been explored and comments on research added to this issue.
• A new detailed issue exists to integrate into GitHub on push for branches if viable to display if checkstyles has increased or decreased in quantity.

Extra Information

A resource which may be of use when looking into the viability which is an existing GitHub action to do just this as a GitHub workflow rather than through Jenkins can be seen below:

• https://github.com/jwgmeligmeyling/checkstyle-github-action

How to Test

verbose instructions for reviewer to test changes
(Add before making a PR)