Closed ButterB0wl closed 4 years ago
Was the IQ server URL using HTTPS?
Yes, it was one of our hosted POC environments behind an https endpoint
it worked for another user hitting the same instance but using a different project if that helps
I tested with a local IQ Server using HTTPS and worked fine. My initial though is this could be a dependencies conflict with other plugin used on the gradle project used for the POC.
This command might give us an idea if that's the case: ./gradlew buildEnvironment
I tested with a local IQ Server using HTTPS and worked fine. My initial though is this could be a dependencies conflict with other plugin used on the gradle project used for the POC.
This command might give us an idea if that's the case:
./gradlew buildEnvironment
That was my initial thought too. Looks like something with Apache org.apache.http.impl.client.HttpClientBuilder.build
Just confirmed that they did this and it worked! thanks so much @guillermo-varela :)
buildscript {
repositories {
maven {
url "https://plugins.gradle.org/m2/"
}
mavenCentral()
}
dependencies {
classpath 'org.sonatype.gradle.plugins:scan-gradle-plugin:1.0.2'
classpath 'org.sonatype.ossindex:ossindex-service-client:1.3.0'
}
}
apply plugin: 'org.sonatype.gradle.plugins.scan'
The key is having together this 2 classpath elements:
classpath 'org.sonatype.gradle.plugins:scan-gradle-plugin:1.0.2'
classpath 'org.sonatype.ossindex:ossindex-service-client:1.3.0'
Just confirmed that they did this and it worked! thanks so much @guillermo-varela :)
buildscript { repositories { maven { url "https://plugins.gradle.org/m2/" } mavenCentral() } dependencies { classpath 'org.sonatype.gradle.plugins:scan-gradle-plugin:1.0.2' classpath 'org.sonatype.ossindex:ossindex-service-client:1.3.0' } } apply plugin: 'org.sonatype.gradle.plugins.scan' The key is having together this 2 classpath elements: classpath 'org.sonatype.gradle.plugins:scan-gradle-plugin:1.0.2' classpath 'org.sonatype.ossindex:ossindex-service-client:1.3.0'
Thanks for the confirmation 👍 I'm currently working on removing the need to have that explicit OSS Index dependency on the classpath, so it should be easier to apply the plugin in the next version.
@ButterB0wl Version 1.0.3
of this plugin has been published fixing all remaining issues, that means people can apply the plugin the simple way:
plugins {
id 'org.sonatype.gradle.plugins.scan' version '1.0.3'
}
Was doing a POC kickoff using the gradle plugin to do some onboarding onto IQ and this is what the prospect ran into. Any idea what could be causing this? Will also ask them to post the build.gradle file here, anything else i should ask for in order to troubleshoot? @guillermo-varela @DarthHater
I reran the gradle steps with the --stacktrace flag, and got some more details that I thought might be helpful. Let me know if there's anything else I can do.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.