Jenkins

Karate afterFeature function execution works fine when run locally but fails when run through Jenkins

由 穿精又带淫゛_ 提交于 2021-02-16 21:00:40
问题 Karate afterFeature function execution works fine when run locally but fails when run through Jenkins, I get assertion failed: assert evaluated to false: responseStatus == 200 || responseStatus == 404 . Whereas the responseStatus should either be 200 or 404 . Code Snippet main.feature snippet Background: ... * def myName1 = 'karate-test-name' * configure afterFeature = function(){ karate.call('cleanup.feature'); } ... ... cleanup.feature @ignore Feature: To cleanup after main.feature

Karate afterFeature function execution works fine when run locally but fails when run through Jenkins

由 半世苍凉 提交于 2021-02-16 21:00:16
问题 Karate afterFeature function execution works fine when run locally but fails when run through Jenkins, I get assertion failed: assert evaluated to false: responseStatus == 200 || responseStatus == 404 . Whereas the responseStatus should either be 200 or 404 . Code Snippet main.feature snippet Background: ... * def myName1 = 'karate-test-name' * configure afterFeature = function(){ karate.call('cleanup.feature'); } ... ... cleanup.feature @ignore Feature: To cleanup after main.feature

Jenkins pipeline with folder plugin. How to build a job located different folder

由 半世苍凉 提交于 2021-02-16 18:07:56
问题 I'm using jenkins 2.0 with Cloudbees Folder plugin as this allow me to create multiple similar projects. The jobs in each folder can be factored out leaving a top level job that can then call a parameterised job. I want to place the parameterised job in a Generic folder and then call them from a pipeline script. So within the jenkins browser I would have 3 folder : ProjA, ProjB and Generic. Under ProjA I have a pipeline job that needs to build a job called TestJib in the generic folder. My

Jenkins pipeline with folder plugin. How to build a job located different folder

由 本秂侑毒 提交于 2021-02-16 18:06:53
问题 I'm using jenkins 2.0 with Cloudbees Folder plugin as this allow me to create multiple similar projects. The jobs in each folder can be factored out leaving a top level job that can then call a parameterised job. I want to place the parameterised job in a Generic folder and then call them from a pipeline script. So within the jenkins browser I would have 3 folder : ProjA, ProjB and Generic. Under ProjA I have a pipeline job that needs to build a job called TestJib in the generic folder. My

Jenkins pipeline with folder plugin. How to build a job located different folder

由 若如初见. 提交于 2021-02-16 18:06:45
问题 I'm using jenkins 2.0 with Cloudbees Folder plugin as this allow me to create multiple similar projects. The jobs in each folder can be factored out leaving a top level job that can then call a parameterised job. I want to place the parameterised job in a Generic folder and then call them from a pipeline script. So within the jenkins browser I would have 3 folder : ProjA, ProjB and Generic. Under ProjA I have a pipeline job that needs to build a job called TestJib in the generic folder. My

【Jenkins】修改Ubuntu下的jenkins端口号

由 会有一股神秘感。 提交于 2021-02-16 08:21:31
jenkins安装目录：/var/lib/jenkins jenkins日志目录：/var/log/jenkins/jenkins.log jenkins默认配置：/etc/default/jenkins 通过检查 /etc/init.d/jenkins 脚本，发现其实就需要做两步： 1. 修改do_start函数的check_tcp_port命令，端口号从8080换成8082 [plain] # # Function that starts the daemon/service # do_start() { # the default location is /var/run/jenkins/jenkins.pid but the parent directory needs to be created mkdir `dirname $PIDFILE` > /dev/null 2>&1 || true chown $JENKINS_USER `dirname $PIDFILE` # Return # 0 if daemon has been started # 1 if daemon was already running # 2 if daemon could not be started $DAEMON $DAEMON_ARGS --running && return 1 #

jenkins搭建

由 淺唱寂寞╮ 提交于 2021-02-15 16:53:00
1，安装包下载地址：https://pkg.jenkins.io/redhat-stable/ 2，安装 rpm -ih jenkins-1.562-1.1.noarch.rpm 安装后生成： /usr/lib/jenkins/jenkins.war WAR包 /etc/sysconfig/jenkins 配置文件 //修改默认端口8080为其他 /var/lib/jenkins/ 默认的JENKINS_HOME目录 /var/log/jenkins/jenkins.log Jenkins日志文件 vim /etc/init.d/jenkins 修改jenkins使用java版本,注释掉不使用的，添加或保留使用的java candidates=" #/etc/alternatives/java #/usr/lib/jvm/java-1.8.0/bin/java #/usr/lib/jvm/jre-1.8.0/bin/java #/usr/lib/jvm/java-1.7.0/bin/java #/usr/lib/jvm/jre-1.7.0/bin/java #/usr/bin/java /usr/local/jdk1.8.0_171/bin/java 3.启动jenkin，sservice jenkins start Starting Jenkins [ OK ] //启动成功 4

Selenium Webdriver 3.X源码分析之webdriver.py(一)

由 南笙酒味 提交于 2021-02-15 04:14:38
点击上方“蓝字”带你去看小星星^_^ > Selenium Webdriver 3.X源码分析系列第16篇，该系列原则上会将整个源码分享一遍 本文主要分享webdriver.py模块中关键组织结构，webdriver.py模块是selenium webdriver最核心的模块，实现了webdriver日常使用的几乎所有的API，是必须掌握的模块。 其源码主要由以下几个方面构成： Licensed说明 依赖模块的导入 python兼容性处理 全局变量和函数 5. webdriver类 未完待续.... Selenium3.X源码分析之开始,走上人生巅峰 Selenium3.X源码分析之异常源码 Selenium Webdriver 3.X源码分析之核心目录结构 Selenium Webdriver 3.X源码分析之核心代码common Selenium Webdriver 3.X源码分析之ActionChains Selenium Webdriver 3.X源码分析之alert.py Selenium Webdriver 3.X源码分析之DesiredCapabilities分布式测试解决方案 Selenium Webdriver 3.X源码分析之定位方式和键盘定义 Selenium Webdriver 3.X源码分析之Proxy.py代理能力 Selenium Webdriver

jenkins插件学习之job-parameter-summary-plugin

由 对着背影说爱祢 提交于 2021-02-14 17:33:46
今天介绍一个插件 job-parameter-summary-plugin Display job parameter summary on main job page 在job主页上显示参数摘要 插件的源码地址: https://github.com/jenkinsci/job-parameter-summary-plugin 插件wiki地址: https://plugins.jenkins.io/job-parameter-summary/ 如下图所示，作用就是在job主页上面显示参数摘要信息。 来源： oschina 链接： https://my.oschina.net/u/4390738/blog/3301712

Docker 数据卷

由 空扰寡人 提交于 2021-02-14 16:13:23
Docker内部数据与容器互连，通过挂载的形式给docker一个外在的数据存储空间。 数据卷 数据卷可以在容器之间共享和重用 对 数据卷的修改会立马生效 对 数据卷的更新，不会影响镜像 默认一直存在，即使容器被删除 数据卷的使用类似于linux的mount 创建数据卷 terry@terry:~$ docker volume create my-vol my-vol 查看数据卷 terry@terry:~$ docker volume ls DRIVER VOLUME NAME local jenkins_home local my-vol 查看指定数据卷 terry@terry:~$ docker inspect jenkins_home [ { "Driver": "local", "Labels": null, "Mountpoint": "/var/lib/docker/volumes/jenkins_home/_data", "Name": "jenkins_home", "Options": {}, "Scope": "local" } ] 启动一个挂载数据卷的容器 docker run -p 8080:8080 -p 50000:50000 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts 删除数据卷
订阅 Jenkins