Automation analysis

Aperta
  • Qualcosa non va?
#164 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
github-actions, java
Ambito
tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
Java
Stelle
13
Fork
33
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di killbill/killbill-analytics-plugin

Tutte le issue di killbill/killbill-analytics-plugin

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.