sceredi / devops-practice

Practice with DevOps

Steps

1. Create a new public GitHub repository "devops-practice" (or really whatever you like), or pick an old project of yours with no build automation nor CI.
2. If you created a new repo, write a program in a JVM-compatible language of your pick (Java, Groovy, Scala, Kotlin).
3. Configure a build system to compile and run the program.
4. Checkpoint: ask the teacher to take a look.
5. Configure the git hooks to make sure that every commit message adheres to a convention (conventional commits are recommended).
6. Configure a CI pipeline that compiles and executes the program on Linux.
7. Create a build matrix for testing with multiple operating systems.
8. Checkpoint: ask the teacher to take a look.
9. Create an empty release job that runs only if the previous ones completed successfully.
10. Configure the program for release on Maven Central. Use of dedicated plugins (e.g., https://github.com/DanySK/publish-on-central) is allowed.
11. Make sure that you can upload and close the project on Maven Central.
12. Make sure that you can upload and close the project on Maven Central automatically.
13. Configure a new job, that runs in parallel with the ones that compile and test, which tests the upload and closure on central (dry-delivery).
14. Make sure that the dry-delivery job runs only in case secrets are available (not on branch builds of forks, nor on pull request builds).
15. Checkpoint: ask the teacher to take a look.
16. Configure the branch protection on the default branch (whatever its name). No PR must be mergeable, unless the CI works, the branch is up to date, and there are no pending discussions.
17. Configure semantic release to release on Central, following the commits convention you adopted.
18. Make a first fully-automated release on Maven Central (if necessary, trick the bot by creating an empty commit with an appropriate message).
19. Checkpoint: ask the teacher to take a look.
20. Configure Renovate to propose updates via pull requests, auto-rebase-merging and auto-rebase-updating the PRs. If you have a centralized shareable configuration, you can reuse it.
21. Checkpoint: ask the teacher to take a look.

Summary

• Kotlin base project
• Gradle
• Conventional Commits
• CI/CD
  • Build + Test with matrix
  • dry-delivery until close repository on Maven Central
  • Semantic Release on
    • GitHub Release
    • Maven Central
• Branch protection
• Renovate

devops-practice's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Use matchDepNames instead of matchPackageNames

This repository currently has no open or pending branches.

Detected dependencies

github-actions

.github/workflows/build-and-deploy.yml

• DanySK/action-checkout 0.2.19
• DanySK/build-check-deploy-gradle-action 3.5.0
• actions/checkout v4.1.7
• actions/setup-node v4.0.3

.github/workflows/dispatcher.yml

gradle

gradle.properties

settings.gradle.kts

• org.gradle.toolchains.foojay-resolver-convention 0.8.0
• org.danilopianini.gradle-pre-commit-git-hooks 2.0.8

app/build.gradle.kts

• org.danilopianini.publish-on-central 5.1.4

gradle/libs.versions.toml

• com.google.guava:guava 33.2.1-jre
• org.jetbrains.kotlin.jvm 2.0.0

gradle-wrapper

gradle/wrapper/gradle-wrapper.properties

• gradle 8.9

npm

package.json

• semantic-release ^24.0.0
• node 20.16

---

• Check this box to trigger a request for Renovate to run again on this repository