This can be helpful for the new features coming to GitHub around security, which will allow us to alert all dependents of any vulnerabilities in a specific version and ask them to update. From the packages view we can also track the number of downloads and other packages using the specific version. As an example, this tag release resulted in this package being published. The release notes from the tag will be copied over as the package description which can be helpful to mention any changes that occured for the new version. I am using the Gradle Kotlin DSL but for more details see the official GitHub Packages documentation on setting up Gradle.įirst we need to include the maven-publish plugin as a dependency in // plugins publish Monitoring PackagesĪfter we have Gradle setup and the GitHub Actions checked in, we can release a new version of our library. Now that we have a successful build, we want to configure Gradle so when we run the publish command it connects to GitHub Packages. This will also help us avoid the common “ it works on my machine” problem. Finally, save this value as a GitHub workflow output: on: push jobs: coverage: runs-on: ubuntu-latest name: Generate test coverage badge steps: - name. Here, I used parse-coverage-report as an example command (you'll need to create it by yourself). This ensures that all contributors to a project are using the same version of Gradle and we can just use the wrapper in the actions. First, you need to parse the coverage result file and extract the value ( 81 in your example). While we can use Gradle in GitHub Actions with some community created steps, I like to use the Gradle Wrapper. The first step is to make sure our library can build locally and the output is a valid jar file.
0 kommentar(er)
