Ugbot / Ugbot/Agentic-Streaming
CI that actually builds and tests everything
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 37
- Forks
- 2
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 28
Description
Currently .github/workflows/ contains only publish-pypi.yml and publish-testpypi.yml — both just build the Python package. Nothing compiles Java or runs any test suite.
Consequence: a compile error in ports/jagentic-core made the entire JVM tree unbuildable from a clean checkout and went unnoticed. Not one finding from the current audit would have been caught by existing CI.
Baseline measured locally (JDK 21) to lock in:
| Surface | Result |
|---|---|
agentic-flink main module |
770 tests, 0 failures, 0 skipped |
jagentic-core |
~80 tests (13 skipped — see #8) |
| ports: kafka-streams / temporal / pekko / pulsar | 2 each |
| ports: spring / quarkus | 0 tests |
agentic-pekko |
14 |
tool-services packs / app |
15 / 11 |
a2a-gateway |
9 |
ports/go |
go vet clean, 6/6 packages pass |
agentic-clj |
64 tests / 249 assertions |
ports/pyagentic |
93 tests |
Also: switch spotless from apply to check in the default lifecycle — it currently rewrites source files on every mvn test/package. Add Dependabot.
Roadmap epic. Detailed findings, file:line citations and sub-tasks live in the AI-grind tracker (project AGS), which is the source of truth for this work. Local dev — build, test, tracking, profiling — is managed with AI-grind.
Tracked as AGS-3 in the devtools-mcp tracker.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/publish-pypi.yml and publish-testpypi.yml, then use the AGS tracker as the source of truth for the detailed findings and sub-tasks. Review the JDK 21 baseline and the listed Java, Go, Clojure, and Python surfaces to define the required CI coverage. Done means CI builds and tests the intended surfaces, spotless runs in check mode, and Dependabot is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, github-actions, go, java, python
- Domain
- build-system, ci-cd, devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100