Reusable GitHub Actions for Maven Projects — Stop Rewriting CI/CD Pipelines

If you’ve worked on multiple Java projects, you’ve probably noticed something frustrating:

Every repository has its own version of a CI/CD pipeline.

Slightly different. Slightly broken. Slightly outdated.

And every time you start a new project, you end up:

• Copying an old GitHub Actions workflow
• Tweaking it to make it work
• Fixing versioning logic
• Relearning release steps
• Debugging the same issues again

It’s repetitive, inconsistent, and honestly… a waste of time.

---

🚨 The Real Pain Points

After going through this multiple times, a few patterns became obvious:

1. No Standardization

Each project defines CI/CD differently.
→ Hard to maintain across teams

2. Versioning is Messy

Manual version bumps, forgotten tags, inconsistent releases.
→ Leads to broken or confusing releases

3. Releases Are Too Manual

Even with automation, there’s still too much friction.
→ Slows down delivery

4. Pipelines Don’t Scale

What works for one repo doesn’t work for ten.
→ No easy way to reuse workflows

---

💡 The Solution: nerv-actions

Instead of rewriting pipelines every time, I built nerv-actions — a set of reusable GitHub Actions workflows for Maven projects.

The idea is simple:

Define CI/CD once. Reuse it everywhere.

---

⚙️ What It Does

1. Analyze commit history
2. Determine semantic version
3. Update Maven project version
4. Build and test
5. Publish artifacts
6. Create GitHub Release

All automated. No manual steps.

---

🔥 What This Fixes

• ✅ Consistent pipelines across all repositories
• ✅ Automatic semantic versioning
• ✅ Fully automated releases
• ✅ Reusable workflows

You stop thinking about CI/CD… and it just works.

---

📦 Minimal Setup

jobs:
  cd:
    uses: czetsuyatech/nerv-actions/.github/workflows/cd.yml@main
    with:
      javaVersion: '25'
    secrets:
      githubAppId: ${{ secrets.NERV_RELEASE_APP_ID }}
      githubAppPrivateKey: ${{ secrets.NERV_RELEASE_APP_PRIVATE_KEY }}
      githubToken: ${{ secrets.GH_PKG_TOKEN }}

That’s it.

---

🧩 When You Start Scaling

The reality is, most teams don’t stay in a single stack.

Eventually, you’ll need:

• Node.js pipelines
• Go releases
• Container builds
• Cross-repository orchestration

To support this, I built nerv-actions Pro.

👉 Request access to Pro workflows: your-email@example.com

---

🛠️ Need Help Setting This Up?

If you want to skip the trial-and-error, I also offer services to:

• Design CI/CD pipelines for your architecture
• Implement GitHub Actions workflows
• Set up automated releases
• Optimize performance and reliability

The goal: a clean, scalable pipeline without the headaches.

👉 Request consulting: your-email@example.com

---

💭 Final Thought

CI/CD shouldn’t be something every project reinvents.

Once standardized, it becomes:

• Predictable
• Maintainable
• Scalable

That’s what nerv-actions is aiming for.

---

🔗 Project Link

• https://github.com/czetsuyatech/nerv-actions
• Demo: https://github.com/czetsuyatech/nerv-audit