Lots of room to improve. Start with a README and CI.

:book: Groovy CheatSheet For Jenkins Usage In A4

Documentation

52

License6pt0

No license detected.

Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

0

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt0

No CI configuration detected in this repository.

If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Project health

33

Dependency manifest6pt0

No dependency manifest detected at root.

Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • Median issue response
  • Median PR merge time
  • 0
    Open issues
Repository files56 root entries
  • .gitignore
    Good: .gitignore present.
  • 00-csrf.groovy
  • 00-disable-cli-remoting.groovy
  • 00-slave-to-master-access.groovy
  • addjobstoview-byregexp.groovy
  • build-monitor-views.xml
  • cheatsheet-jenkins-groovy-A4.pdf
  • check-slave-jar-version.groovy
  • config-pipeline-library.groovy
  • config-slack.groovy
  • create-jenkins-job.groovy
  • create-jenkins-user.groovy
  • create-secret-text.groovy
  • delete-job-by-regexp.groovy
  • dict-to-json.groovy
  • docker-cleanup.groovy
  • enable-ldap.groovy
  • execute-command.groovy
  • files-folder.groovy
  • find-dead-executors.groovy
  • get-env.groovy
  • get-ip-by-hostname.groovy
  • git-checkout.groovy
  • git-commits-before-fail.groovy
  • git-list-tags-and-branches.groovy
  • jenkins-kubernetes-cloud.groovy
  • jenkins-permission.groovy
  • jenkins-url.groovy
  • jenkins-views.groovy
  • jenkins.security.QueueItemAuthenticatorConfiguration.xml
  • jenkinsfile-finally.groovy
  • jenkinsfile-parallelly.groovy
  • jenkinsfile-pass-parameter.groovy
  • jenkinsfile-sequentially.groovy
  • jenkinsfile-timeout-retry.groovy
  • json-file.groovy
  • keep-going-with-errors.groovy
  • kill-queued-jenkins.groovy
  • list-all-jenkins-agent.sh
  • list-all-jobs.groovy
  • logged-in-users.groovy
  • loop-map.groovy
  • manage-jenkins-jobs.groovy
  • master-executors.groovy
  • matrix-authorization-strategy.groovy
  • multi-line-string.groovy
  • print.groovy
  • README.org
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • regexp-match.groovy
  • relative-path.groovy
  • set-agent-env.groovy
  • slack-notification.groovy
  • split-string.groovy
  • string-to-json.groovy
  • timezone.groovy
  • validate-kubernetes-cloud.groovy