Skip to content

Commit

Permalink
Update README.md to reflect the current demo config
Browse files Browse the repository at this point in the history
This repo uses GitHub Actions as of #15 but the `README.md` appears to not have been updated to reflect accordingly.
  • Loading branch information
ChrisCarini authored Sep 30, 2022
1 parent f604dbf commit f729d2c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ Use it as a reference to automate your project!
## Overview

This project represents a development model where every change on the main development branch will produce a new release via the CI system.
The release is a Maven publication (jars, poms) that get uploaded to a free public repository (Maven Central) via a free CI system (Travis).
We chose Maven Central and Travis CI as examples - you can use any system of your choice (for example: JFrog Artifactory + GH Actions).
The release is a Maven publication (jars, poms) that get uploaded to a free public repository (Maven Central) via a free CI system (GitHub Actions).
We chose Maven Central and GitHub Actions as examples - you can use any system of your choice (for example: JFrog Artifactory + Travis CI).
The Gradle plugins we chose for this use case represent the minimum set of Gradle plugins to conveniently automate the releases.

- the Maven publication (jars, poms) is configured using Gradle's built-in [maven-publish](https://docs.gradle.org/current/userguide/publishing_maven.html) plugin.
Expand Down

0 comments on commit f729d2c

Please sign in to comment.