Automation analysis

Open
#164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, java
Domain
tooling

Research direction

Review the automation maturity summary and the linked thesis wiki, especially the recommendations for package management and static code style analysis. Compare those recommendations with the repository's existing GitHub workflows and Maven plugins, which the issue says were analyzed. Done means providing feedback on whether the analysis is correct and useful, or identifying anything it missed.

Written by the indexing model from the issue text.

Description

I'm with the Software Engineering Research Group at the TU Delft, and I am investigating automations. I have looked at your repository and which GitHub workflows and Maven plugins you are using. I'll give you a quick summary of what I found, and the automation tasks I recommend you to focus on next (:

Image

Level of maturity Basic Intermediate Advanced
Collaboration ‎
✅ Completed this level!

✔️ Prepare or create documentation artifacts
✔️ Generate documentation from source code
✔️ Bot commits
❌ Commit validation
❌ Publish documentation
❌ Issues or PRs management
Code quality ‎
⚠️ Still working on this level!

✔️ Run tests
❌ Static code style analysis
✔️ Automatic code formatting
✔️ Static code quality analysis
❌ Test coverage and validity
❌ Generate test reports
✔️ Verify packaging correctness
✔️ Sign artifacts
✔️ License checks
❌ Vulnerability scans
Development ‎
⚠️ Still working on this level!

✔️ Build environment configuration
❌ Package management
✔️ Build files configuration
❌ Optimization
Artifacts ‎
✅ Completed this level!

✔️ Code compilation
✔️ Dependency management of artifact
✔️ Build tasks, resources and configuration
✔️ Packaging
✔️ Generate source and metadata artifacts
✔️ Source code version control
✔️ Release tagging
✔️ Publish artifacts to a registry
❌ Generate release notes
❌ Containerization
❌ Push container to remote

And now? Next steps!

It is not always clear which automation tasks should be prioritized. It is however important to balance your automation efforts, as a uniform level of maturity is most productive. I'm here to help! Below is a list of tasks that you can work on to help level up your maturity across the automation domains:

What do you think?

Do you think my analysis is correct, do these recommendations help you? Or have I missed something?

For my master's thesis I'm doing research into the use of automations in GitHub repositories. With my findings, I want to see if I can help out developers with what automations they could focus on. Do you want to help me out? Leaving a response is much appreciated!

Dominant language
Java
Stars
13
Forks
33
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from killbill/killbill-analytics-plugin

All issues in killbill/killbill-analytics-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.