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

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

相关推荐
脑子加油站2 天前
K8S-Ingress资源对象
算法·贪心算法·k8s
xmlhcxr3 天前
从 0 到 1 落地企业级 DevOps CI/CD 流水线:基于 GitLab+Jenkins+Harbor 的完整实践
运维·docker·gitlab·jenkins·harbor·devops
高旭的旭3 天前
GitLab Omnibus Docker 内存优化实战:从 4.7 GiB 降到 3.2 GiB
docker·容器·gitlab
~黄夫人~4 天前
Kubernetes 入门到实战:概念详解 + kubeadm 安装 + 节点克隆全流程
linux·运维·学习·k8s·集群
牛奶咖啡137 天前
Git实践——GitLab服务器的部署与使用
gitlab·gitlab是什么·gitlab有啥用·gitlab适用场景·gitlab的版本如何选·安装部署gitlab·gitlab的使用
lisanmengmeng8 天前
Gitlab搭建
gitlab
dapeng-大鹏10 天前
记一次 GitLab Let‘s Encrypt 证书申请失败的排查与修复
gitlab
yunson_Liu10 天前
aws EKS集群pvc存储扩容
k8s·aws
身如柳絮随风扬10 天前
使用 Docker 部署 GitLab 并分配用户账号 —— 保姆级教程
docker·容器·gitlab
鼎道开发者联盟11 天前
鼎享会 | 从手工到自动化:OpenClaw改造GitLab内部协作流程的全过程
自动化·gitlab·openclaw