CloudOS5.0企业应用中编译构建在配置完代码库、maven库及构建步骤后,代码检查通过无错误,在执行持续交付中的编译构建时候出现错误,一直无法通过,编译构建运行详细日志如下:
2025-04-07 11:58:27 Cause of Fluxes Service. Jenkins instance default-execution-cluster. pipeline: null (0), Job: hello-devops-build , execution: 0, jobExecution: 1909093388058099712
2025-04-07 11:58:27 using: GITLAB_REPOSITORY http://x.x.x.x http://x.x.x.x/pgdq/hello-devops [SecretStringAuthentication UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: DOCKER-REGISTRY hub.xx.xx [UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: MAVEN_REPOSITORY x.x.x.x:8081 [UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: PAAS-COMMON-USER-CONTEXT null [SecretStringAuthentication ]
2025-04-07 11:58:27 using: PAAS-DOCKER-REGISTRY http://os-hcr-svc.cloudos-paas.svc:15400 []
2025-04-07 11:58:27 using: DOCKER-REGISTRY os-harbor-svc.default.svc.cloudos:443 [UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: DOCKER-REGISTRY os-harbor-svc.default.svc:443 [UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: DOCKER-REGISTRY os-harbor-svc.default:443 [UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: DOCKER-REGISTRY registry.cluster.local:9999 [UsernamePasswordAuthentication ]
2025-04-07 11:58:27 using: TREASURY http://os-treasury-svc:21220
2025-04-07 11:58:27 Resume disabled by user, switching to high-performance, low-durability mode.
2025-04-07 11:58:29 [Pipeline] timestamps
2025-04-07 11:58:29 [Pipeline] {
2025-04-07 11:58:29 [Pipeline] timeout
2025-04-07 11:58:29 Timeout set to expire in 2 hr 0 min
2025-04-07 11:58:29 [Pipeline] {
2025-04-07 11:58:29 [Pipeline] echo
2025-04-07 11:58:29 ============== Start Pipeline ==============
2025-04-07 11:58:29 [Pipeline] echo
2025-04-07 11:58:29 BUILD_VERSION=v20250407115827610
2025-04-07 11:58:29 [Pipeline] echo
2025-04-07 11:58:29 builderImage: os-harbor-svc.default.svc.cloudos:443/helm/h3ccloud/cicd/jenkins-jnlp-agent:dind-centos-universal-M220815
2025-04-07 11:58:29 [Pipeline] echo
2025-04-07 11:58:29 pod namespace ''
2025-04-07 11:58:29 [Pipeline] podTemplate
2025-04-07 11:58:29 [Pipeline] {
2025-04-07 11:58:29 [Pipeline] node
2025-04-07 11:58:44 Still waiting to schedule task
2025-04-07 11:58:44 Waiting for next available executor
2025-04-07 13:58:29 Cancelling nested steps due to timeout
2025-04-07 13:58:29 [Pipeline] // node
2025-04-07 13:58:29 [Pipeline] }
2025-04-07 13:58:29 [Pipeline] // podTemplate
2025-04-07 13:58:29 [Pipeline] }
2025-04-07 13:58:29 [Pipeline] // timeout
2025-04-07 13:58:29 [Pipeline] echo
2025-04-07 13:58:29 org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
2025-04-07 13:58:29 [Pipeline] collectBuildInfo
2025-04-07 13:58:29 ==> collect build information: {"type":"COLLECTED_DATA","buildTicket":{"jobExecutionId":1909093388058099712,"token":"1f26e2b9a493472d93776624181b12f0","backendJobIdentity":"job_1906538880555810816","backendBuildIdentity":null},"messageId":"126dd671-4c44-4236-a5f8-26a341e10746","parameters":{"BUILD_VERSION":"v20250407115827610"}}
2025-04-07 13:58:29 [Pipeline] }
2025-04-07 13:58:29 [Pipeline] // timestamps
2025-04-07 13:58:29 [Pipeline] End of Pipeline
2025-04-07 13:58:29 clear credentials: 49a4acf5-7f6b-4938-8adf-cecd6c376da1
2025-04-07 13:58:29 ==> try to synchronize status CANCELED with fluxes service
2025-04-07 13:58:29 Timeout has been exceeded
2025-04-07 13:58:29 Finished: ABORTED
大神帮忙看看什么原因,如何解决?单一镜像在应用管理都可以成功部署并访问,自动化流水线不行。
(0)
您好,建议您按照以下步骤排查问题:
podTemplate 和镜像配置,确保可以正常拉取镜像。
(0)
这跟把日志上传deepseek分析的一样,一是目前云平台资源,这个排除,二是代码库及镜像库在我自建的k8s+Jenkins环境下可以正常拉取构建部署镜像,已测试完成,排除这个原因,就剩下H3C CloudOS环境下相关配置问题,能否给出具体的解决方案?
编译构建失败可能有多种原因,常见的有以下几种:
1. 代码库、maven库等配置错误:检查代码库、maven库等配置是否正确,是否存在路径、用户名、密码等错误。
2. 构建工具问题:检查构建工具是否正确安装和配置,是否存在版本不兼容等问题。
3. 代码问题:检查代码是否存在错误,是否有编译错误、语法错误等。
4. 资源问题:检查服务器资源是否充足,是否存在内存不足、磁盘空间不足等问题。
建议按照以上思路逐一排查,如果仍然无法解决问题,可以查看编译构建的日志文件,获取更详细的错误信息,以便进一步分析和解决。
(0)
一是目前云平台资源,这个排除,二是代码库及镜像库在我自建的k8s+Jenkins环境下可以正常拉取构建部署镜像,已测试完成,排除这个原因,就剩下H3C CloudOS环境下相关配置问题,能否给出具体的解决方案?
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
这跟把日志上传deepseek分析的一样,一是目前云平台资源,这个排除,二是代码库及镜像库在我自建的k8s+Jenkins环境下可以正常拉取构建部署镜像,已测试完成,排除这个原因,就剩下H3C CloudOS环境下相关配置问题,能否给出具体的解决方案?