beam-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Jenkins Server <>
Subject Build failed in Jenkins: beam_PreCommit_CommunityMetrics_Cron #1908
Date Sun, 23 Feb 2020 06:07:20 GMT
See <>


Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on apache-beam-jenkins-15 (beam) in workspace <>
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository
 > git init <>
# timeout=10
Fetching upstream changes from
 > git --version # timeout=10
 > git fetch --tags --progress +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url # timeout=10
Fetching upstream changes from
 > git fetch --tags --progress +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision a537ae6a2f6a4f51b7108b0d036d1cb1563476b2 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a537ae6a2f6a4f51b7108b0d036d1cb1563476b2
Commit message: "[BEAM-9344] Add support for bundle finalization execution to the Beam Java
SDK. (#10910)"
 > git rev-list --no-walk a537ae6a2f6a4f51b7108b0d036d1cb1563476b2 # timeout=10
No emails were triggered.
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - Injecting as environment variables the properties content 

[EnvInject] - Variables injected successfully.
[Gradle] - Launching build.
[src] $ <>
--continue --max-workers=12 -Dorg.gradle.jvmargs=-Xms2g -Dorg.gradle.jvmargs=-Xmx4g :communityMetricsPreCommit
Starting a Gradle Daemon, 1 busy Daemon could not be reused, use --status for details
> Task :buildSrc:compileJava NO-SOURCE
> Task :buildSrc:compileGroovy FROM-CACHE
> Task :buildSrc:pluginDescriptors
> Task :buildSrc:processResources
> Task :buildSrc:classes
> Task :buildSrc:jar
> Task :buildSrc:assemble
> Task :buildSrc:spotlessGroovy
> Task :buildSrc:spotlessGroovyCheck
> Task :buildSrc:spotlessGroovyGradle
> Task :buildSrc:spotlessGroovyGradleCheck
> Task :buildSrc:spotlessCheck
> Task :buildSrc:pluginUnderTestMetadata
> Task :buildSrc:compileTestJava NO-SOURCE
> Task :buildSrc:compileTestGroovy NO-SOURCE
> Task :buildSrc:processTestResources NO-SOURCE
> Task :buildSrc:testClasses UP-TO-DATE
> Task :buildSrc:test NO-SOURCE
> Task :buildSrc:validateTaskProperties FROM-CACHE
> Task :buildSrc:check
> Task :buildSrc:build
Configuration on demand is an incubating feature.
> Task :beam-test-infra-metrics:composeUp FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':beam-test-infra-metrics:composeUp'.
> Exit-code 255 when calling docker-compose, stdout: postgresql uses an image, skipping
  prometheus uses an image, skipping
  pushgateway uses an image, skipping
  alertmanager uses an image, skipping
  Building grafana
  [18069] Failed to execute script docker-compose
  Traceback (most recent call last):
    File "bin/docker-compose", line 6, in <module>
    File "compose/cli/", line 71, in main
    File "compose/cli/", line 127, in perform_command
    File "compose/cli/", line 287, in build
    File "compose/", line 386, in build
    File "compose/", line 368, in build_service
    File "compose/", line 1084, in build
    File "site-packages/docker/api/", line 260, in build
    File "site-packages/docker/api/", line 307, in _set_auth_headers
    File "site-packages/docker/", line 310, in get_all_credentials
    File "site-packages/docker/", line 262, in _resolve_authconfig_credstore
    File "site-packages/docker/", line 287, in _get_store_instance
    File "site-packages/dockerpycreds/", line 25, in __init__
  dockerpycreds.errors.InitializationError: docker-credential-gcloud not installed or not
available in PATH

* Try:
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.

* Get more help at

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.

1 actionable task: 1 executed

Publishing build scan...

Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message