Automation analysis

オープン
  • 何か問題がありますか？
#164 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
ドキュメント
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
github-actions, java
領域
tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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!

主要言語
Java
スター
13
フォーク
33
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

killbill/killbill-analytics-plugin のほかの issue

killbill/killbill-analytics-plugin の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。