k8s gitlab cicd 之gradle 篇章(二)并发打包问题

前文:https://caicongyang.blog.csdn.net/article/details/132049822?spm=1001.2014.3001.5502

运行几天后发现以下问题:

Starting a Gradle Daemon, 4 busy and 2 stopped Daemons could not be reused, use --status for details

FAILURE: Build failed with an exception.

html 复制代码
$ chmod 777 gradlew
$ ./gradlew build -x test
Starting a Gradle Daemon, 4 busy and 2 stopped Daemons could not be reused, use --status for details

FAILURE: Build failed with an exception.

* What went wrong:
Gradle could not start your build.
> Could not create service of type ResourceSnapshotterCacheService using GradleUserHomeServices.createResourceSnapshotterCacheService().
   > Timeout waiting to lock file hash cache (/cache/itwork/gradle/repository/caches/6.8/fileHashes). It is currently in use by another Gradle instance.
     Owner PID: 97
     Our PID: 97
     Owner Operation: 
     Our operation: 
     Lock file: /cache/itwork/gradle/repository/caches/6.8/fileHashes/fileHashes.lock

* 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 https://help.gradle.org

BUILD FAILED in 1m 47s
ERROR: Job failed: command terminated with exit code 1

大概意思是就是无法并发打包;

修改后的ci文件如下:

html 复制代码
stages:
  - package
  - docker-build

package:
  stage: package
  script:
    - export GRADLE_USER_HOME=${GRADLE_USER_HOME}/${GROUP_NAME}/${CI_PROJECT_NAME}/.gradle
    - export PATH=GRADLE_USER_HOME/bin:$PATH
    - echo $GRADLE_USER_HOME
    - chmod 777 gradlew
    - ./gradlew build -x test
    - cp build/libs/app.jar ${CACHE_PIPELINE}/app.jar
  only:
    - master
    - tags
    - /^feature-.*$/
    - /^hotfix-.*$/
    - /^bugfix-.*$/
docker-build:
  stage: docker-build
  script:
    - update_dockerfile
    - docker_build .
    - update_charts_base v3 server
    - chart_build
  only:
    - master
    - tags
    - /^release-.*$/
    - /^hotfix-.*$/
    - /^bugfix-.*$/
    - /^feature-.*$/

.auto_devops: &auto_devops |
  http_status_code=`curl -o .auto_devops.sh -s -m 10 --connect-timeout 10 -w %{http_code} "${CHOERODON_URL}/devops-action/ci?gitlabProjectId=${CI_PROJECT_ID}&pipelineId=${CI_PIPELINE_ID}&token=${Token}&type=base&version=v1"`
  if [ "$http_status_code" != "200" ]; then
    cat .auto_devops.sh
    exit 1
  fi
  source .auto_devops.sh
before_script:
  - *auto_devops

核心修改点: 打包阶段每个项目设置不同的打包目录

  • export GRADLE_USER_HOME={GRADLE_USER_HOME}/{GROUP_NAME}/${CI_PROJECT_NAME}/.gradle

  • export PATH=GRADLE_USER_HOME/bin:$PATH

不知道各位大佬有没有更好的方法呢

相关推荐
Algorithm15762 小时前
mac上使用docker搭建gitlab
macos·docker·gitlab
binqian15 小时前
【CICD】GitLab Runner 和执行器(Executor
gitlab
极小狐19 小时前
GitLab 如何跨版本升级?
gitlab·devsecops·devops·极狐gitlab·安全合规
Suhw1 天前
借助 Pause 容器调试 Pod
k8s·pause容器
运维小文2 天前
K8资源之endpoint资源&EP资源
linux·网络·k8s·运维开发
xixingzhe22 天前
gitlab角色、权限
gitlab
小安运维日记2 天前
CKA认证 | Day1 k8s核心概念与集群搭建
运维·云原生·容器·kubernetes·云计算·k8s
KubeSphere 云原生2 天前
云原生周刊:Istio 1.24.0 正式发布
云计算·k8s·容器平台·kubesphere
Source、2 天前
gitlab和jenkins连接
运维·gitlab·jenkins
公西雒3 天前
关于在GitLab的CI/CD中用docker buildx本地化多架构打包dotnet应用的问题
ci/cd·docker·gitlab·qemu·dotnet