gradle-nexus-staging-plugin | Automatize releasing Gradle projects to Maven Central | Continous Integration library

by Codearte Groovy Version: 0.30.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | gradle-nexus-staging-plugin Summary

gradle-nexus-staging-plugin is a Groovy library typically used in Devops, Continous Integration, Gradle, Jenkin, Maven applications. gradle-nexus-staging-plugin has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A gradle plugin providing tasks to close and promote/release staged repositories. It allows to do a full artifacts release to Maven Central through Sonatype OSSRH (Open Source Software Repository Hosting) without the need to use Nexus GUI (to close and release artifacts/repository).

Support

Quality

Security

License

Reuse

Support

gradle-nexus-staging-plugin has a low active ecosystem.

It has 148 star(s) with 22 fork(s). There are 8 watchers for this library.

It had no major release in the last 12 months.

There are 9 open issues and 85 have been closed. On average issues are closed in 326 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gradle-nexus-staging-plugin is 0.30.0

Quality

gradle-nexus-staging-plugin has no bugs reported.

Security

gradle-nexus-staging-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

gradle-nexus-staging-plugin is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gradle-nexus-staging-plugin releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-nexus-staging-plugin

Get all kandi verified functions for this library.

gradle-nexus-staging-plugin Key Features

No Key Features are available at this moment for gradle-nexus-staging-plugin.

gradle-nexus-staging-plugin Examples and Code Snippets

No Code Snippets are available at this moment for gradle-nexus-staging-plugin.

Community Discussions

Trending Discussions on gradle-nexus-staging-plugin

Gradle uploadArchives from Travis mangles staging repositories

QUESTION

Gradle uploadArchives from Travis mangles staging repositories

Asked 2018-Oct-15 at 21:47

I have an open source project that hooks to travis-ci.org and that builds with gradle.

This project uses the gradle maven plugin to upload release artifacts to oss.sonatype.org using the uploadArchives target. What usually happens is that this target creates a single staging repository in Sonatype, then the Gradle nexus staging plugin promotes the repository and it shows up in Maven Central a few minutes later.

However, recently, the uploadArchives target started creating multiple staging repositories, each with a partial subset of the artifacts needed; and that happens only when run in Travis, not when I try from a laptop.

What am I missing here, which makes it work locally when running ./gradlew uploadArchives, but fail in Travis?

A few links which might help:

...

ANSWER

Answered 2018-Oct-15 at 21:47

In the end it appears this is a common error that started appearing this year. Travis VMs with sudo: enabled or docker will change IP addresses between artifact uploads and this will prompt Sonatype to think those artifacts belong to different repositories. Adding this to my travis.yml fixed it:

Source https://stackoverflow.com/questions/52788386

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gradle-nexus-staging-plugin

Add gradle-nexus-staging-plugin to the buildscript dependencies in your build.gradle file for root project:.
The plugin itself does not upload any artifacts. It only closes/promotes a repository with all already uploaded using the maven or maven-publish plugin artifacts (in the same or previous Gradle execution). Therefore it is enough to apply io.codearte.nexus-staging only on the root project in a multi-project build.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: