jenkins api部署时，一直提示pending-Finished waiting

最新推荐文章于 2024-09-04 17:49:43 发布
原创 最新推荐文章于 2024-09-04 17:49:43 发布 · 718 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#jenkins #运维 #python

问题：

调用jenkins api部署时，一直提示pending-Finished waiting

解决方案：

这个问题困扰了很久，一直没有思路，后面看到调用jenkinsAPI本身会出现一段提示，pending in the quiet period，通过搜索这个提示，才了解到是静默期的问题，通过把静默期取消，就可以解决了

bug_rabbit
关注
k8s 重新部署 jenkins 后一直 Pending【排查分析】
甘蓝的专栏
07-30 547
K8s 中重新部署 jenkins，发现一直Pending，怎么破？
Jenkins+Gitlab+Ansible自动化部署（六）
Liqiufeng_的博客
08-12 2632
Jenkins+Gitlab+Ansible自动化部署(2021-08-12) Pipeline Job实现Nginix+MySQL+PHP+Wordpress实现自动化部署交付 一、环境准备 编写ansible playbook脚本实现Wordpress远程部署 将wordpress源码与playbook部署脚本提交到gitlab仓库 编写pipeline job脚本实现Jenkins流水线持续交付流程 Jenkins集成Ansible与gitlab实现wordpress的自动化部署 二、验证环境
Jenkins触发任务一直报错(pending—Waiting for next available executor on
weixin_45443274的博客
08-18 3294
一开始理解，任务a完成后，节点机器应该就被释放了，可以继续完成任务b，实际上现在构建的a触发b是在一个任务里，要这个整体的任务完成后，才能继续执行下一个任务，而在这个任务里走到任务b的时候，虽然任务a已经完成了，但是整体的任务没有完成，导致任务b一直在pending状态，陷入死循环。jenkins构建任务a，把代码从库里拉下来后编译版本并上传到ftp服务器，任务a完成后，自动触发任务b运行自动化用例。设置了1，执行器的数量定义了这个节点可以执行的并发数，所以这里只需要把执行器的数量改一下就行了。
Jenkins构建时提示pending—Waiting for next available executor
baiyuan99的博客
10-18 2940
Jenkins重启后，导致所有项目构建时都提示pending—Waiting for next available executor，选择master配置，点击“刷新状态”，发现其他项目都能正常构建，但是有一个项目还是会一直提示。1. 点击系统管理–》节点配置—》选择master配置从节点，将执行器数量增大即可。索性将该异常的项目删除掉重新创建一次，再次构建正常。2.删除了一些之前构建的记录，也没有解决问题。最终也没有找到什么原因，删除重建也是一种方法。配置自动丢弃构建历史数据，3.前面操作那些之后。
Jenkins执行任务一直显示pending—Waiting for next available executor
IChen.的博客
06-25 1万+
一 问题 Jenkins执行任务时一直显示pending—Waiting for next available executor . 二 排查问题 1.检查设置的执行者数量 并没有超过设置的值 2.检查节点 发现master有叉叉 点击名称进入详情页，能够看到具体信息。原因是磁盘满了 三 解决 1.自动丢弃构建历史数据 修改策略为以下 2.关于以前有些Jenkins Job被删除但是WorkSpace没有被清理的问题 正常的删除Jenkins Job的流程是 先清理工作空间 然后再删除掉Jenk
Jenkins持续集成显示pending—Waiting for next available executor
zhichuan0307的博客
08-28 5712
问题： 早上jenkins持续集成时，一直开始不了，然后查看显示，一直报pending—Waiting for next available executor，大意是等待下个执行，当前节点的可以执行的数量已经达到了最大量，所以，jenkins再添加一个是，需要一直等待。 解决： 点击系统管理--》节点配置---》选择master配置从节点，将执行器数量增大即可。 ...
看下这段日志，问题是什么？ Started by user Devops CRD Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] echo Original Release Version: 280 [Pipeline] node Running on Jenkins in /root/.jenkins/workspace/tapocare-app-blue-green-pipeline-new [Pipeline] { [Pipeline] withEnv [Pipeline] { [Pipeline] timestamps [Pipeline] { [Pipeline] stage [Pipeline] { (Sync Up Release) [Pipeline] echo 15:45:36 Sync up tapocare-app release ... [Pipeline] script [Pipeline] { [Pipeline] echo 15:45:36 Major Deploy Version: 1.39.903 [Pipeline] sh 15:45:37 + AWS_DEFAULT_REGION=ap-southeast-1 AWS_PROFILE=uat helm repo update 15:45:37 Hang tight while we grab the latest from your chart repositories... 15:45:45 ...Successfully got an update from the "prd-tplink-nbu" chart repository 15:45:45 Update Complete. ⎈ Happy Helming!⎈ [Pipeline] sh 15:45:45 + helm search repo prd-tplink-nbu/tapocare-app --version 1.39.903 [Pipeline] sh 15:45:48 + cat ./temp 15:45:48 + grep -w prd-tplink-nbu/tapocare-app 15:45:48 + head -1 15:45:48 + cut -f 2 [Pipeline] echo 15:45:48 RELEASE_VERSION: 1.39.903 [Pipeline] echo 15:45:48 Latest Release Version: 1.39.903 [Pipeline] } [Pipeline] // script [Pipeline] echo 15:45:48 Creating build directories ... [Pipeline] sh 15:45:49 + mkdir ./build-280 [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Authorization) Stage "Authorization" skipped due to when conditional [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Promote Stage) [Pipeline] input 15:45:49 Promote to uat-v2.ap-southeast-1? 15:45:49 Proceed or Abort 15:45:58 Approved by Devops CRD [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy Stage) [Pipeline] echo 15:45:58 Deploying tapocare-app Release v1.39.903 to uat-v2.ap-southeast-1 ... [Pipeline] dir 15:45:58 Running in /root/.jenkins/workspace/tapocare-app-blue-green-pipeline-new/build-280 [Pipeline] { [Pipeline] script [Pipeline] { [Pipeline] sh 15:45:58 + + git ls-remote ssh://cicdtplinknbu@pdgerrit.tp-link.com:29418/tplinknbu/devops_cicd mastercut 15:45:58 -f1 [Pipeline] echo 15:45:58 commit id: a3e6c3d3b3868522155f9fbf2189ad35b8832f23 15:45:58 94f29bae0d31af8a54e32e5bcb5d6e59af3b0978 [Pipeline] sh 15:45:59 + rm -rf devops_cicd 15:45:59 + mkdir devops_cicd [Pipeline] sh 15:45:59 + git clone --depth 1 -b master ssh://cicdtplinknbu@pdgerrit.tp-link.com:29418/tplinknbu/devops_cicd 15:45:59 Cloning into 'devops_cicd'... 15:46:01 Total 26276 (delta 8564), reused 21366 (delta 8564) 15:46:03 Updating files: 99% (18692/18803) Updating files: 100% (18803/18803) Updating files: 100% (18803/18803), done. [Pipeline] sh 15:46:03 + rm -rf k8s-values 15:46:03 + mkdir k8s-values [Pipeline] sh 15:46:03 + cp -rf ./devops_cicd/k8s-values/tapocare-app ./k8s-values/ [Pipeline] sh 15:46:04 + rm -rf ./devops_cicd [Pipeline] echo 15:46:04 ENV: pet-v2 [Pipeline] echo 15:46:04 deploy() begins... [Pipeline] sh 15:46:04 + yq read ./k8s-values/tapocare-app/pet/ap-southeast-1/values.yaml app.namespace [Pipeline] sh 15:46:04 + kubectl get deployment -n pet-app-ipc --context uat-v2.ap-southeast-1 [Pipeline] sh 15:46:06 + cat ./temp 15:46:06 + grep -E tapocare-app-[0-9]+(\.[0-9,a-z,A-Z]+)+(-[a-z,A-Z]+)* 15:46:06 + cut -d -f 1 [Pipeline] echo 15:46:06 PREVIOUS_DEPLOY: tapocare-app-1.37.20 [Pipeline] sh 15:46:07 + kubectl get deployment tapocare-app-1.37.20 -o yaml -n pet-app-ipc --context uat-v2.ap-southeast-1 [Pipeline] sh 15:46:08 + cat ./temp 15:46:08 + yq read - spec.template.metadata.labels."app.kubernetes.io/version" [Pipeline] echo 15:46:08 pet PREVIOUS_VER: 1.37.20 [Pipeline] echo 15:46:08 Deploying to pet: ap-southeast-1 [Pipeline] sh 15:46:09 + kubectl get hpa tapocare-app-1.37.20 -o yaml -n pet-app-ipc --context uat-v2.ap-southeast-1 [Pipeline] sh 15:46:10 + + cat ./temp 15:46:10 yq read - spec.minReplicas [Pipeline] sh 15:46:10 + kubectl get hpa tapocare-app-1.37.20 -o yaml -n pet-app-ipc --context uat-v2.ap-southeast-1 [Pipeline] sh 15:46:12 + yq read - spec.maxReplicas 15:46:12 + cat ./temp [Pipeline] sh 15:46:12 + kubectl get deployment tapocare-app-1.37.20 -o yaml -n pet-app-ipc --context uat-v2.ap-southeast-1 [Pipeline] sh 15:46:14 + cat ./temp 15:46:14 + yq read - spec.replicas [Pipeline] echo 15:46:14 ONLINE_MIN_REPLICAS: 1 [Pipeline] echo 15:46:14 ONLINE_MAX_REPLICAS: 1 [Pipeline] echo 15:46:14 CURRENT_REPLICAS: 1 [Pipeline] sh 15:46:14 + yq read ./k8s-values/tapocare-app/pet/ap-southeast-1/values.yaml autoscaling.maxReplicas [Pipeline] sh 15:46:14 + yq write -i ./k8s-values/tapocare-app/pet/ap-southeast-1/values.yaml replicaCount 1 [Pipeline] sh 15:46:15 + yq write -i ./k8s-values/tapocare-app/pet/ap-southeast-1/values.yaml autoscaling.minReplicas 1 [Pipeline] sh 15:46:15 + yq write -i ./k8s-values/tapocare-app/pet/ap-southeast-1/values.yaml autoscaling.maxReplicas 1 [Pipeline] echo 15:46:15 ONLINE_MAX_REPLICAS: 1 [Pipeline] echo 15:46:15 CURRENT_REPLICAS: 1 [Pipeline] sh 15:46:15 + [ -d ./k8s-values/tapocare-app/pet ] 15:46:15 + echo true [Pipeline] sh 15:46:15 + [ -d ./k8s-values/tapocare-app/global ] 15:46:15 + echo true [Pipeline] sh 15:46:16 + [ -d ./k8s-values/tapocare-app/pet/common ] 15:46:16 + echo true [Pipeline] sh 15:46:16 + [ -d ./k8s-values/tapocare-app/pet/ap-southeast-1/config ] 15:46:16 + echo true [Pipeline] sh 15:46:16 + kubectl create configmap tapocare-app-pet-ap-southeast-1-tmp-config --from-file=./k8s-values/tapocare-app/global --from-file=./k8s-values/tapocare-app/pet/common --from-file=./k8s-values/tapocare-app/pet/ap-southeast-1/config --dry-run -o=yaml [Pipeline] sh 15:46:17 + yq read tapocare-app-pet-ap-southeast-1-tmp.yaml data [Pipeline] sh 15:46:17 + yq prefix -i tapocare-app-pet-ap-southeast-1-config-map-data.yaml configMap.data [Pipeline] sh 15:46:17 + [ -d ./k8s-values/tapocare-app/pet/ap-southeast-1 ] 15:46:17 + echo true [Pipeline] sh 15:46:17 + echo NEW_RELEASE_NAME tapocare-app-1.39.903 15:46:17 NEW_RELEASE_NAME tapocare-app-1.39.903 [Pipeline] sh 15:46:18 + helm list --namespace pet-app-ipc --kube-context uat-v2.ap-southeast-1 [Pipeline] sh 15:46:20 + cat ./temp 15:46:20 + grep tapocare-app 15:46:20 + head -1 15:46:20 + cut -f 1 [Pipeline] sh 15:46:20 + echo networking init 15:46:20 networking init [Pipeline] sh 15:46:20 + kubectl apply -f ./k8s-values/tapocare-app/pet/ap-southeast-1/networking/service.yaml --context pet-v2.ap-southeast-1 15:46:22 service/tapocare-app-aps1 unchanged [Pipeline] sh 15:46:22 + kubectl apply -f ./k8s-values/tapocare-app/pet/ap-southeast-1/networking/istio.yaml --context pet-v2.us-east-1 15:46:24 gateway.networking.istio.io/tapocare-app-aps1-gw unchanged 15:46:24 virtualservice.networking.istio.io/tapocare-app-aps1-vs unchanged 15:46:24 virtualservice.networking.istio.io/tapocare-app-aps1-internal-vs unchanged 15:46:24 gateway.networking.istio.io/tapocare-app-aps1-internal-grpc-gw unchanged 15:46:24 virtualservice.networking.istio.io/tapocare-app-aps1-internal-grpc-vs unchanged [Pipeline] sh 15:46:24 + echo networking init successfully 15:46:24 networking init successfully [Pipeline] sh 15:46:25 + AWS_DEFAULT_REGION=ap-southeast-1 AWS_PROFILE=uat helm upgrade --install tapocare-app-1.39.903 prd-tplink-nbu/tapocare-app --version 1.39.903 --values ./k8s-values/tapocare-app/pet/ap-southeast-1/values.yaml --values tapocare-app-pet-ap-southeast-1-config-map-data.yaml --namespace pet-app-ipc --kube-context uat-v2.ap-southeast-1 --timeout 1200s --wait 15:46:26 Release "tapocare-app-1.39.903" does not exist. Installing it now. 16:06:47 Error: timed out waiting for the condition [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Blue-Green Release) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] stage [Pipeline] { (Promote To BLUE-GREEN-TEST) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy To BLUE-GREEN-TEST) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Promote To BLUE-GREEN-ALL) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy To BLUE-GREEN-ALL) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (SCALE-DOWN-BLUE) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Promote To BLUE-GREEN-END) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy To BLUE-GREEN-END) Stage "Blue-Green Release" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Test stage) Stage "Test stage" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE
最新发布
11-18
从日志分析，部署失败的核心原因是**Helm安装超时**（`timed out waiting for the condition`），具体发生在部署新版本`tapocare-app-1.39.903`时。以下是详细分析： --- ### **根本问题** ```log 15:46:25 helm ...
不使用K8S和Docker Swarm的情况下,纯Docker环境下nginx+hyperf+pm2的部署方案
jobsen123的专栏
07-16 4786
一 、构建Php镜像，其镜像包含pm2和pm2-logrotate以及ssh公钥登录功能 Dockerfile FROM ubuntu:18.04 MAINTAINER jobsen123@qq.com ENV DEBIAN_FRONTEND noninteractive RUN sed -i -e s@/archive.ubuntu.com/@/mirrors.aliyun.com/@g -e s@/security.ubuntu.com/@/mirrors.aliyun.com/@g /etc/.
K8s NetworkPolicy、LimitRange和ResourceQuota详解、K8s运行ZooKeeper,Mysql,Jenkins集群、K8s集群及应用监控Prometheus
weixin_42896216的博客
04-02 4239
NetworkPolicy详解、K8s运行ZooKeeper,Mysql,Jenkins,Wordpress集群,K8s LimitRange和ResourceQuota资源限制详解、K8s集群及应用监控Prometheus
Tekton简介，安装和构建最简单ci/cd
09-04 881
本文介绍了tekton是什么，如何安装，以及实践了下task和task run
jenkins Pending quiet period关闭静默期
MinisterZ的博客
01-07 1541
关掉静默期 Manage jenkins-> Configure System ->Quiet Period
在python代码中关闭正在执行的Jenkins Job
EvaHdil1L的博客
11-08 536
使用python直接关闭正在运行的jenkins的job
Hudson的build一直提示pending-waiting for next available executor
Rainman的专栏
11-18 8029
发现系统的CIE环境中Hudson一直提示pending-waiting for next available executor, 而不执行build任务，等了好久都没反应，重启一下tomcat后发现好用了，不过下次执行build又开始提示waiting for next available executor后来发现是因为tomcat所在的目录所剩磁盘空间太少了，把tomcat目录移到另外一个
jenkins -pending—Waiting for next available executor on 主服务器
热门推荐
zhuchunyan_aijia的博客
08-09 1万+
在jenkins 构建任务时，同时只能构建2个，如果两个没有job没有结束，构建第3个就会不执行： 提示： pending—Waiting for next available executor on 主服务器 通过设置节点中一下配置 # of executors：最大同时构建数量 根据机器的性能定，单颗四核cpu建议不要超过5)【必须为数字】 在系统管理-节点管理， 选择对应节点，点击...
jenkins -pending—Jenkins is reserved for jobs with matching label expression
zhuchunyan_aijia的博客
08-09 6532
在系统管理--管理节点 选择节点，配置从节点  改成：  
Jenkins 更新主目录问题及解决方案记录
一壁蔷薇枝
03-20 4884
最近jenkins服务器做build的时候发现有问题，显示“pending - waiting for next executor”，检查发现home directory磁盘空间已经只剩100多MB，于是决定更换home directory, 在这个过程中走了一些弯路，记录一下历程，以供他人参考。切换home directory 历程jenkins 安装背景系统： 14.04.1-Ubuntu 该
Celery-UserGuide-Tasks
JosephThatwho的博客
12-17 516
任务时celery的组成要素。 任务是由任意可调用对象创建的类。任务包含双重角色，因为它既定义了调用任务（发送消息）时发生的事情，也定义了工人/worker接收到该消息时发生的情况。 每个任务类都含有唯一的名称，这个名称会在人物信息中引用，worker通过这个名称执行正确的函数。 任务信息会被保留在队列中，直到worker确认任务信息。一个工人可以预先保留许多信息，即使工人因停电或其他原因死亡，消息也会重新传递给另一个工人。 理想情况下，任务函数应该是幂等的：这意味着即使使用相同的参数多次调用该函数也不会产
掌握Jenkins管道：使用workflow-step-api-plugin编写自定义步骤
workflow-step-api-plugin是一个为Jenkins流水线提供扩展性的插件，它允许开发者通过添加自定义的步骤到流水线中。 3. Java与Groovy： workflow-step-api-plugin是基于Java语言开发的，而Jenkinsfile通常是用Groovy...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值