I am confused, if my credentials weren't properly ...
# community-support
c
I am confused, if my credentials weren't properly set then my build wouldn't work because I need those to pull artifacts from another project (I think... maybe the cache is screwing me) https://github.com/xenoterracide/spring-app-commons/blob/main/.github/workflows/publish.yml
Copy code
with:
    cache-disabled: false
    cache-read-only: false
    cache-write-only: false
    cache-overwrite-existing: false
    gradle-home-cache-includes: caches
  notifications
  
    gradle-home-cache-cleanup: false
    add-job-summary: always
    add-job-summary-as-pr-comment: never
    dependency-graph: generate-and-submit
    dependency-graph-continue-on-failure: false
    artifact-retention-days: 1
    build-scan-publish: false
    generate-job-summary: true
    gradle-home-cache-strict-match: false
    workflow-job-context: null
    github-token: ***
  env:
    ORG_GRADLE_PROJECT_ghUsername: 
    ORG_GRADLE_PROJECT_ghPassword: ***
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.4-7/x64
    JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.4-7/x64
    GRADLE_ACTION_ID: gradle/actions/setup-gradle
    GRADLE_BUILD_ACTION_SETUP_COMPLETED: true
    GRADLE_BUILD_ACTION_CACHE_RESTORED: true
    GRADLE_ENCRYPTION_KEY: ***
    DEVELOCITY_INJECTION_INIT_SCRIPT_NAME: gradle-actions.inject-develocity.init.gradle
    DEVELOCITY_AUTO_INJECTION_CUSTOM_VALUE: gradle-actions
    GITHUB_DEPENDENCY_GRAPH_ENABLED: false
  
Gradle setup only performed on first gradle/actions step in workflow.
Enabling dependency graph generation
/home/runner/work/spring-app-commons/spring-app-commons/gradlew -Dorg.gradle.configureondemand=false -Dorg.gradle.dependency.verification=off -Dorg.gradle.unsafe.isolated-projects=false :ForceDependencyResolutionPlugin_resolveAllDependencies
Error: The operation was canceled.
https://github.com/xenoterracide/spring-app-commons/actions/runs/10836958024/job/30071850943
wait... I think the build might be getting killed
it took a minute to publish a half dozen jars? where each should be measured in kilobytes? tf... that seems extreme
yep, that appears to be it, it succeeds on its latest run which would also have more cache hits, and so is under 5 minutes.
anyone know if there's a way to see what the actual size of the artifacts generated and a final average transfer speed? so I could find out why it took 60 seconds? I can transfer gigabytes at home faster and I imagine githubs internal network is more optimized. maybe nevermind