Jenkins高级篇之Pipeline技巧篇-4-根据参数传入条件控制执行不同stage

最新推荐文章于 2023-04-17 17:43:48 发布
最新推荐文章于 2023-04-17 17:43:48 发布
阅读量1.6w 收藏 24
点赞数 2
分类专栏： Jenkins高级篇之Pipeline代码自动化 DevOps/CI/CD工程师入门系列 文章标签： Pipeline技巧篇 条件控制stage的执行
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u011541946/article/details/89322510
版权

这篇我来介绍一下之前，很早的时候介绍pipeline语法的时候，有一个指令叫when 和expression，当时由于pipeline知识学习太少，不好举例子去学习消化。到了这里，其实这两个关键字就是用来控制stage的执行，如果你条件有好几个，可以精确控制让哪一些stage执行，让哪一些stage不执行。

我这里举例一个自动化测试中的例子，例如我写了多个stage，这个pipeline脚本执行执行冒烟测试，和集成测试。有时候，我们希望快速执行冒烟测试，想根据结果看看，不一定一上来就执行集成测试。为了达到这种控制效果，我们就需要使用逻辑控制。在pipeline中就使用when 和expression两个命令。例如，如果json文件中冒烟测试变量为true，我就只执行冒烟测试的stage,其他和冒烟测试无关的stage我就不去执行。如果冒烟测试变量值为false，也就是默认要跑集成测试（不跑冒烟测试）。为了不搞得这么复杂，我们就分两个类型测试就好。下面，我用pipeline代码方式去实现。

1.json准备

{
  "NAME" : "Lucy",
  "AGE" : "18",
  "PHONE_NUMBER" : "13912345678",
  "ADDRESS" : "Haidian Beijing",
  "EMAIL" : "lucy@demo.com",
  "GENDER" : "male",
  "SMOKE": true,
  "IS_MARRY" : false
}

我还是在前面文章的/tmp/anthony/test.json文件基础上加了一个变量 SMOKE， 默认值是true。

2.pipeline stage groovy文件代码

由于我添加了一个SMOKE的变量，所以在初始化stage，我们新增一行代码，初始化SMOKE的变量。

import hudson.model.*;


pipeline{ 
	
	agent any
	stages{
		stage("Hello Pipeline") {
			steps {
			    script {
					println "Hello Pipeline!"
					println env.JOB_NAME
					println env.BUILD_NUMBER
				}
			}
		}
		
		stage("Init paramters in json") {
			steps {
			    script {
					println "read josn input file"
					json_file = INPUT_JSON? INPUT_JSON.trim() : ""
					prop = readJSON file : json_file
					name = prop.NAME? prop.NAME.trim() : ""
					println "Name:" + name
					age = prop.AGE? prop.AGE.trim() : ""
					println "Age:" + age
					phone = prop.PHONE_NUMBER? prop.PHONE_NUMBER.trim() : ""
					println "Phone:" + phone
					address = prop.ADDRESS? prop.ADDRESS.trim() : ""
					println "Address:" + address
					email = prop.EMAIL? prop.EMAIL.trim() : ""
					println "Email:" + email
					gender = prop.GENDER? prop.GENDER.trim() : ""
					println "Gender:" + gender
					is_marry = prop.IS_MARRY? prop.IS_MARRY : false
					println "is_marry:" + is_marry
					is_smoke = prop.SMOKE? prop.SMOKE : false
                                        println "is_smoke:" + is_smoke
				}
			}
		}
		stage("call a method") {
			steps {
			    script {
					println "send the parameter as map type"
					model_call = load env.WORKSPACE + "/groovy/projectA-model.groovy"
					model_call.getUserInfo(name:name, age:age, phone:phone, address:address, email:email, gender:gender, is_marry:is_marry)
				}
			}
		}
		stage("check serive up") {
		    when {
		        expression {
		            return (is_smoke == true)
		        }
		    }
		    steps {
			    script {
					println "SMOKE TEST: check service startup"
				}
			}
		}
        stage("check UI login") {
	        when {
			    expression {
			        return (is_smoke == true)
			    }
			}
		    steps {
			    script {
					println "SMOKE TEST: check UI login success"
				}
			}
		}
		
		stage("Integrate-ModelA") {
	        when {
			    expression {
			        return (is_smoke == false)
			    }
			}
		    steps {
			    script {
					println "Integrate-ModelA"
				}
			}
		}
		
		stage("Integrate-ModelB") {
	        when {
			    expression {
			        return (is_smoke == false)
			    }
			}
		    steps {
			    script {
					println "Integrate-ModelB"
				}
			}
		}
	}

}

3.测试效果

只跑冒烟测试，也就是SMOKE的值在json中是true

我这里直接贴出运行日志

Started by user root
Rebuilds build #9
Rebuilds build #15
Rebuilds build #16
Rebuilds build #17
Obtained src/Jenkinsfile/projectA-stages.groovy from git https://github.com/Anthonyliu86/pipeline-skills-demo.git
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/lib/jenkins/workspace/ProjectA-pipeline-demo
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential 03214975-2168-4795-981a-ddd935f62a76
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/Anthonyliu86/pipeline-skills-demo.git # timeout=10
Fetching upstream changes from https://github.com/Anthonyliu86/pipeline-skills-demo.git
 > git --version # timeout=10
using GIT_ASKPASS to set credentials 
 > git fetch --tags --progress https://github.com/Anthonyliu86/pipeline-skills-demo.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 35f0fbe78b205b5e0cdbf94444722411a7ebdb62 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 35f0fbe78b205b5e0cdbf94444722411a7ebdb62
Commit message: "fix"
 > git rev-list --no-walk ff9cbf42c55cb87c863bb6b96d511ccc496eff80 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Hello Pipeline)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
Hello Pipeline!
[Pipeline] echo
ProjectA-pipeline-demo
[Pipeline] echo
18
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Init paramters in json)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
read josn input file
[Pipeline] readJSON
[Pipeline] echo
Name:Lucy
[Pipeline] echo
Age:18
[Pipeline] echo
Phone:13912345678
[Pipeline] echo
Address:Haidian Beijing
[Pipeline] echo
Email:lucy@demo.com
[Pipeline] echo
Gender:male
[Pipeline] echo
is_marry:false
[Pipeline] echo
is_smoke:true
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (call a method)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
send the parameter as map type
[Pipeline] load
[Pipeline] { (/var/lib/jenkins/workspace/ProjectA-pipeline-demo/groovy/projectA-model.groovy)
[Pipeline] }
[Pipeline] // load
[Pipeline] echo

	Lucy come from Haidian Beijing, he is 18 old. he's phone number is
	13912345678, or you can contact he via lucy@demo.com, he is not marry yet.
	
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check serive up)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
SMOKE TEST: check service startup
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check UI login)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
SMOKE TEST: check UI login success
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Integrate-ModelA)
Stage "Integrate-ModelA" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Integrate-ModelB)
Stage "Integrate-ModelB" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS

只跑集成测试，先去test.json把SMOKE的值改成false

Started by user root
Rebuilds build #9
Rebuilds build #15
Rebuilds build #16
Rebuilds build #17
Obtained src/Jenkinsfile/projectA-stages.groovy from git https://github.com/Anthonyliu86/pipeline-skills-demo.git
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/lib/jenkins/workspace/ProjectA-pipeline-demo
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential 03214975-2168-4795-981a-ddd935f62a76
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/Anthonyliu86/pipeline-skills-demo.git # timeout=10
Fetching upstream changes from https://github.com/Anthonyliu86/pipeline-skills-demo.git
 > git --version # timeout=10
using GIT_ASKPASS to set credentials 
 > git fetch --tags --progress https://github.com/Anthonyliu86/pipeline-skills-demo.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 35f0fbe78b205b5e0cdbf94444722411a7ebdb62 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 35f0fbe78b205b5e0cdbf94444722411a7ebdb62
Commit message: "fix"
 > git rev-list --no-walk ff9cbf42c55cb87c863bb6b96d511ccc496eff80 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Hello Pipeline)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
Hello Pipeline!
[Pipeline] echo
ProjectA-pipeline-demo
[Pipeline] echo
18
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Init paramters in json)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
read josn input file
[Pipeline] readJSON
[Pipeline] echo
Name:Lucy
[Pipeline] echo
Age:18
[Pipeline] echo
Phone:13912345678
[Pipeline] echo
Address:Haidian Beijing
[Pipeline] echo
Email:lucy@demo.com
[Pipeline] echo
Gender:male
[Pipeline] echo
is_marry:false
[Pipeline] echo
is_smoke:true
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (call a method)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
send the parameter as map type
[Pipeline] load
[Pipeline] { (/var/lib/jenkins/workspace/ProjectA-pipeline-demo/groovy/projectA-model.groovy)
[Pipeline] }
[Pipeline] // load
[Pipeline] echo

	Lucy come from Haidian Beijing, he is 18 old. he's phone number is
	13912345678, or you can contact he via lucy@demo.com, he is not marry yet.
	
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check serive up)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
SMOKE TEST: check service startup
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check UI login)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
SMOKE TEST: check UI login success
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Integrate-ModelA)
Stage "Integrate-ModelA" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Integrate-ModelB)
Stage "Integrate-ModelB" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS

再看看stage view的图片效果

其实，如果你还可以利用第二个参数，写在expression中，来控制当什么条件符合的时候，执行全部的冒烟加上集成测试，这样的效果都是可以实现的。

json文件如下

{
  "NAME" : "Lucy",
  "AGE" : "18",
  "PHONE_NUMBER" : "13912345678",
  "ADDRESS" : "Haidian Beijing",
  "EMAIL" : "lucy@demo.com",
  "GENDER" : "male",
  "SMOKE": false,
  "FULL_TEST":true,
  "IS_MARRY" : false
}

stage 代码修改如下

import hudson.model.*;


pipeline{ 
	
	agent any
	stages{
		stage("Hello Pipeline") {
			steps {
			    script {
					println "Hello Pipeline!"
					println env.JOB_NAME
					println env.BUILD_NUMBER
				}
			}
		}
		
		stage("Init paramters in json") {
			steps {
			    script {
					println "read josn input file"
					json_file = INPUT_JSON? INPUT_JSON.trim() : ""
					prop = readJSON file : json_file
					name = prop.NAME? prop.NAME.trim() : ""
					println "Name:" + name
					age = prop.AGE? prop.AGE.trim() : ""
					println "Age:" + age
					phone = prop.PHONE_NUMBER? prop.PHONE_NUMBER.trim() : ""
					println "Phone:" + phone
					address = prop.ADDRESS? prop.ADDRESS.trim() : ""
					println "Address:" + address
					email = prop.EMAIL? prop.EMAIL.trim() : ""
					println "Email:" + email
					gender = prop.GENDER? prop.GENDER.trim() : ""
					println "Gender:" + gender
					is_marry = prop.IS_MARRY? prop.IS_MARRY : false
					println "is_marry:" + is_marry
					is_smoke = prop.SMOKE? prop.SMOKE : false
					println "is_smoke:" + is_smoke
					full_test = prop.FULL_TEST? prop.FULL_TEST : false
				}
			}
		}
		stage("call a method") {
			steps {
			    script {
					println "send the parameter as map type"
					model_call = load env.WORKSPACE + "/groovy/projectA-model.groovy"
					model_call.getUserInfo(name:name, age:age, phone:phone, address:address, email:email, gender:gender, is_marry:is_marry)
				}
			}
		}
		stage("check serive up") {
		    when {
		        expression {
		            return (is_smoke == true || full_test == true)
		        }
		    }
		    steps {
			    script {
					println "SMOKE TEST: check service startup"
				}
			}
		}
        stage("check UI login") {
	        when {
			    expression {
			        return (is_smoke == true || full_test == true)
			    }
			}
		    steps {
			    script {
					println "SMOKE TEST: check UI login success"
				}
			}
		}
		
		stage("Integrate-ModelA") {
	        when {
			    expression {
			        return (is_smoke == false || full_test == true)
			    }
			}
		    steps {
			    script {
					println "Integrate-ModelA"
				}
			}
		}
		
		stage("Integrate-ModelB") {
	        when {
			    expression {
			        return (is_smoke == false || full_test == true)
			    }
			}
		    steps {
			    script {
					println "Integrate-ModelB"
				}
			}
		}
	}

}

测试结果

Anthony_tester
关注
  • 2
    点赞
  • 踩
  • 24
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
jenkins 用Pipeline实现控制stage任务进行精确构建发布
weixin_43546282的博客
02-15 482
jenkins 用Pipeline实现控制stage任务进行精确构建发布
Jenkins Pipeline 流水线
最新发布
qq_42944740的博客
03-22 1146
Jenkins 流水线是一套插件，它集成持续交付流水线到 Jenkins。流水线提供了一组可扩展的工具，用于通过流水线语法将简单到复杂的交付流水线建模为“代码”.对流水线的定义通常写在一个文本文件中​​，该文件可以被提交到项目的源代码的控制仓库，这是"流水线即代码"的表现形式。​​能使用两种语法进行编写 - 声明式和脚本化。相比脚本化的流水线语法，声明式提供更丰富的语法特性,声明式是为了使编写和读取流水线代码更容易而设计的。然而，现实情况中，写到​。
Jenkins高级篇之Pipeline技巧篇-4-根据参数传入条件控制执行不同stage.rar
09-16
Jenkins高级篇之Pipeline技巧篇-4-根据参数传入条件控制执行不同stage.rar
Jenkins Pipeline定义不同Stage的共享变量
LiRunChao3的博客
05-26 3298
pipeline { agent any stages { stage('输入'){ steps{ script{ dirInput = input message: "填写信息",ok: "同意", parameters: [ string(name: 'Applicant', defaultValue: ' ', descript
Jenkins pipeline 通过构建参数定义stage是否执行。
qq_40402603的博客
07-07 2563
背景 在公司项目中有这样的需要。一个 jenkins job 有多个开发人员使用。但是每个开发人员都编译不用的代码模块。希望实现通过 build 时自选模块。完成各自构建。 解决方案 使用 自定义环境变量的方式来控制stage是否执行。废话不多说。直接讲解pipeline. 设置完成后web效果如下，这样在pipeline中。$model_name 就等于 所选择的字符串，且用逗号分割。 例如我们勾选pdk 和 ethfw 。则 $model_name = 'pdk,ethfw' 如果我们...
[jenkins]-jenkins流水线根据是否是定时触发执行部分stage
爷来辣的博客
04-17 671
导语：jenkins 流水线有个.git比较大的job，还在测试阶段，经常1个多月不部署，导致job里下载的git等被清理。这个 Stage 配置定时构建，即每周一次。其他 Stage 并没有配置构建触发器，所以不会受到定时构建的影响。要在 pipeline 中实现这个功能，您需要在 pipeline 脚本中添加。语句来限制只有指定的模块或路径中的代码更改时才执行对应的构建操作。希望这个示例能够帮助您实现 pipeline 定期构建的需求。希望这个示例能够帮助您实现针对 Stage 的定时构建需求。
Jenkins Pipeline 动态参数传入
隔壁老瓦的专栏
04-19 2595
https://www.cnblogs.com/lvcisco/p/12048879.html pipeline 多个参数如何传入 https://www.cnblogs.com/tarzen213/p/15875034.html pipeline中sh使用参数化构建输入的参数 充分利用pipeline自身的特性 pipeline 多个参数如何传入 - lvelvis - 博客园1.准备一个json文件 /tmp/Anthony/test.json写入上面的内容，保存，这个路径下面会用到 2.修改
Jenkins高级篇之Pipeline技巧篇-2-如何处理多个参数化变量.rar
09-16
Jenkins高级篇之Pipeline技巧篇-2-如何处理多个参数化变量.rar
Jenkins高级篇之Pipeline技巧篇-3-JSON文件处理多个参数进一步优化.rar
09-16
Jenkins高级篇之Pipeline技巧篇-3-JSON文件处理多个参数进一步优化.rar
Jenkins高级篇之Pipeline技巧篇-1-小白搭建Pipeline项目开发环境.rar
09-16
Jenkins高级篇之Pipeline技巧篇-1-小白搭建Pipeline项目开发环境.rar
Jenkins高级篇之Pipeline语法篇-9-多个stage的关系：顺序和并行
热门推荐
Anthony_tester的博客
11-01 3万+
在Declarative Pipeline模式的代码中，可能会在一个stages{…}中声明一窜嵌套的stages{…}, 并以顺序执行。需要指出的是，一个stage{…}必须有且只有一个steps{…}, 或者parallel{…} 或者stages{…} 看看下面这个顺序嵌套例子代码 pipeline { agent none stages { stage...
Jenkins parameters trigger pipeline plugin 一个pipeline触发另外pipeline并传递参数
云原生，DevOps，Kubernetes
12-05 2198
使用插件：parameters trigger pipeline plugin 传参数pipeline： pipeline { agent {label 'java'} environment { branch = 'release/1.0' module = 'demo' } stages { stage ('Pull...
Jenkins job 之间实现带参数触发
Linda的自动化测试之旅
06-30 1万+
开发打包的 jenkins job A 是在 local 的一台 windows 上，同时在这台 local 的 windows 上还有一 另一个 jenkins job B 是用来上传 job A 生成的包（build）到测试平台的仓库（比如 saucelabs storage）。然而 我们测试的 jenkins job C 是在 azure 上的一台 windows server 2012 上。
Jenkins高级篇之Pipeline语法篇-7-Declarative Pipeline指令：triggers/stage/tool
Anthony_tester的博客
10-30 9145
本篇继续学习Declarative Pipeline的相关指令，本篇学习三个指令，分别是触发器（triggers），stage和tool。触发器主要是方便周期控制自动化提交，stage是在stages{...}下的一个指令，我们平台的大部分代码都在stage内完成，tool主要就是为了三大工具（jdk, gradle,maven）提供环境变量服务的。 指令1：triggers 该trigger...
【Jenkins pipeline】语法详解
hupengfei_shenyang的博客
02-02 830
jenkins pipeline 总体介绍 pipeline 是一套运行于jenkins上的工作流框架，将原本独立运行于单个或者多个节点的任务连接起来，实现单个任务难以完成的复杂流程编排与可视化。 pipeline 是jenkins2.X 最核心的特性， 帮助jenkins 实现从CI 到 CD与 DevOps的转变 pipeline 提供一组可扩展的工具， 通过 pipeline domain specific language syntax 可以到达pipeline as code 目的 pipili
jenkins-pipeline语法详解
chenjxj123的博客
11-15 4442
在声明式的pipeline中默认无法使用脚本语法，但是pipeline提供了一个脚本环境入口：script{},通过使用script来包裹脚本语句，即可使用脚本语法。6.input:指令允许暂时中断pipeline执行，等待用户输入，根据用户输入进行下一步动作。通过将阶段设置为parallel来表明该stage为并行运行，但是需要注意以下几点。pipeline声明式具体代码使用示例：(自动打最新版本apk并执行自动化)引用的工具需要在管理页面的全局工具配置里配置过。5.tools:用于引用配置好的工具。
jenkins pipeline基础语法与示例
06-29 680
一、Jenkins介绍 二、Jenkins Pipeline介绍 Jenkins Pipeline总体介绍 1.Pipeline 是Jenkins 2.X核心特性，帮助Jenkins实现从CI到CD与DevOps的转变 2.Pipeline 简而言之，就是一套运行于Jenkins上的工作流框架，将原本独立 运行于单个或者多个节点的任务连接起来，实现单个任务难以完成的复杂流 程编排与可视化。 什么是Jenkins Pipeline 1.Jenkins Pipeline是一组插...
pipeline之stage（二）
wfhh000的专栏
01-23 3459
在真正的RISC IC的制成中，不会只有这五个stage。它可能存在多条pipeline，每条pipeline 有多个stage。如： integer ALU：有5个stage； FP/integer multiplication（浮点/integer乘）：大概有11个stage 由于每条指令的the number of stages不同，就可也能够造成较多的问题： 1、有些指令
jenkins高级篇之pipeline语法篇
04-11
Jenkins高级篇Pipeline语法篇是指Jenkins Pipeline的高级语法部分，该部分可以实现更为复杂的流水线构建操作，例如并行构建、多分支构建等。它涉及到Jenkinsfile的编写，并且需要一定的编程能力和经验。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值