search

RedPillAnalytics / gradle-confluent

Apache License 2.0
22 stars 10 forks source link

Issue building project due to access/missing GCS maven repo #88

Closed jeffreylutz closed 4 years ago

jeffreylutz commented 4 years ago

Describe the bug I attempt to build the project using the instructions of "./gradlew build'. An error occurs due to access/missing resource to Caused by: org.gradle.api.resources.ResourceException: Could not get resource 'gcs://maven.redpillanalytics.io/demo/com/redpillanalytics/simple-build-pipeline/maven-metadata.xml'

To Reproduce Steps to reproduce the behavior:

  1. Checkout master branch
  2. type: './gradlew build'
  3. An error occurs
  4. Caused by: org.gradle.api.resources.ResourceException: Could not get resource 'gcs://maven.redpillanalytics.io/demo/com/redpillanalytics/simple-build-pipeline/maven-metadata.xml'

Expected behavior The build succeeds with the build artifact produced

Desktop (please complete the following information):

Additional context

./gradlew build

Task :groovydoc Trying to override old definition of task fileScanner

Task :test WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.codehaus.groovy.reflection.CachedClass (file:/Users/jeffreylutz/.gradle/wrapper/dists/gradle-6.3-bin/8tpu6egwsccjzp10c1jckl0rx/gradle-6.3/lib/groovy-all-1.3-2.5.10.jar) to method java.lang.Object.finalize() WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.reflection.CachedClass WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release

LoadConfigTest

Test Application Plugin expand works with default file PASSED (5.3s) Test Application Plugin expand works with relative file PASSED Test Application Plugin expand works with absolute file PASSED Test Application Plugin expand works with absolute file and environment PASSED Test Application Plugin expand works with absolute file and bogus environment PASSED Test Application Plugin applicationDefaultJvmArgs are replaced PASSED

TasksTest

Test classMethod FAILED

org.gradle.testkit.runner.UnexpectedBuildFailure: Unexpected build execution failure in /Users/jeffreylutz/code/odot/gradle-confluenut/build/tmp/test/run-tasks with arguments [-Si, tasks, --all, showConfiguration]

Output: The client will now receive all logging from the daemon (pid: 29361). The daemon log file: /var/folders/6t/m14czhws2r1dlkmkqr0cj4kw0000gn/T/.gradle-test-kit-jeffreylutz/test-kit-daemon/6.3/daemon-29361.out.log Starting 7th build in daemon [uptime: 6.617 secs, performance: 99%, non-heap usage: 14% of 268.4 MB] Closing daemon's stdin at end of input. The daemon will no longer process any standard input. Using 8 worker leases. Starting Build Settings evaluated using settings file '/Users/jeffreylutz/code/odot/gradle-confluenut/build/tmp/test/run-tasks/settings.gradle'. Projects loaded. Root project using build file '/Users/jeffreylutz/code/odot/gradle-confluenut/build/tmp/test/run-tasks/build.gradle'. Included projects: [root project 'run-tasks']

Configure project : Evaluating root project 'run-tasks' using build file '/Users/jeffreylutz/code/odot/gradle-confluenut/build/tmp/test/run-tasks/build.gradle'. Resource missing. [HTTP GET: https://jcenter.bintray.com/com/redpillanalytics/simple-build-pipeline/maven-metadata.xml] Closing Git repo: /Users/jeffreylutz/code/odot/gradle-confluenut/.git

FAILURE: Build failed with an exception.

Results: FAILURE (7 tests, 6 successes, 1 failures, 0 skipped)

FAILURE: Executed 7 tests in 14.3s (1 failed)

7 tests completed, 1 failed There were failing tests. See the report at: file:///Users/jeffreylutz/code/odot/gradle-confluenut/build/reports/tests/test/index.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 19s 14 actionable tasks: 14 executed

stewartbryson commented 4 years ago

Growing pains of having other developers contribute. I need to refit to not use GCS buckets as Maven repos for testing KSQL artifacts, as of course, not everyone has access to those.

The test in question is DeployTest. I simply need to put that artifact file in resources, and define it as a gradle flatDir maven repository.

stewartbryson commented 4 years ago

PR #90 resolves this issue. All tests that previously used GCS buckets now use a directory that exists in the test/resources directory, which is copied into the test workspace using Ant.