search

unbroken-dome / gradle-testsets-plugin

A plugin for the Gradle build system that allows specifying test sets (like integration or acceptance tests).
MIT License
230 stars 50 forks source link

Gradle 6.6.1 is unable to get testsets module on repo #113

Open zatenzu opened 4 years ago

zatenzu commented 4 years ago

Hi,

I'm trying to use gradle-testsets-plugin v 3.0.1 with gradle 6.6.1:

plugins { id "org.unbroken-dome.test-sets" version "3.0.1" }

The build fails because gradle is unable to get the module from the repo (see build logs below). If I understand well what is happened, gradle detected https://plugins.gradle.org/m2/ as a maven repo so it read gradle-testsets-plugin-3.0.1.pom file. Inside it, there was the 'published-with-gradle-metadata' key, so gradle decided to search for .module file in the same repo and it didn't exist. Because of that, gradle get HTTP 303 redirection to the jfrog repo but the plugin is not present on it and the build failed.

So my question is, why the 'published-with-gradle-metadata' key is specified in the pom file without .module file on the gradle plugins repo and what can I do to build my app successfully?

TIA,

[Gradle failure report] FAILURE: Build failed with an exception. [16:27:43] [Gradle failure report] [16:27:43] [Gradle failure report] What went wrong: [16:27:43] [Gradle failure report] A problem occurred configuring root project 'evs-phoenix-sequence-view'. [16:27:43] [Gradle failure report] > Could not resolve all artifacts for configuration ':classpath'. [16:27:43] [Gradle failure report] > Could not resolve org.unbroken-dome.gradle-plugins:gradle-testsets-plugin:3.0.1. [16:27:43] [Gradle failure report] Required by: [16:27:43] [Gradle failure report] project : > org.unbroken-dome.test-sets:org.unbroken-dome.test-sets.gradle.plugin:3.0.1 [16:27:43] [Gradle failure report] > Could not resolve org.unbroken-dome.gradle-plugins:gradle-testsets-plugin:3.0.1. [16:27:43] [Gradle failure report] > Could not get resource 'https://plugins.gradle.org/m2/org/unbroken-dome/gradle-plugins/gradle-testsets-plugin/3.0.1/gradle-testsets-plugin-3.0.1.module'. [16:27:43] [Gradle failure report] > Could not GET 'https://repo.jfrog.org/artifactory/libs-release-bintray/org/unbroken-dome/gradle-plugins/gradle-testsets-plugin/3.0.1/gradle-testsets-plugin-3.0.1.module?referrer'. [16:27:43] [Gradle failure report] > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [16:27:43] [Gradle failure report] [16:27:43] [Gradle failure report] Try: [16:27:43] [Gradle failure report] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. [16:27:43] [Gradle failure report] [16:27:43] [Gradle failure report] * Get more help at https://help.gradle.org [16:27:43] [Gradle failure report] [16:27:43] [Gradle failure report] BUILD FAILED in 15s

jeffbswope commented 4 years ago

This is also breaking our builds here where the missing module eventually leads to hitting network security snafus as it follows redirects searching for it and eventually hits blocked urls...

I've had to work around it by manually deploying to our internal repo (which is checked before the plugin portal) with an altered pom.

alexanderLinear commented 3 years ago

i would like to better understand that, including native methods to work around that. i am seeing a similar problem when running my gradle based builds in a non-networked fashion.