Jenkins

JNLP Connections are deprecated in Jenkins what is the new recommended way connecting a windows slave to jenkins?

由 梦想与她 提交于 2020-04-16 05:45:10
问题 As the Title already states JNLP Connections are Deprecated Jenkins also gives a Message and a Hyperlink to https://en.wikipedia.org/wiki/Java_Web_Start#Deprecation So whats now the recommended way attaching a Windows Slave to Jenkins, there seems to be no real good guide on https://jenkins.io covering that topic. 回答1: Open Source Alternative There is an open source replacement called OpenWebStart which is based on IcedTeaWeb. More information: Java Web Start is dead - long live OpenWebStart!

Run jenkins agent in docker container, issue with jenkins pipeline and /var/run/docker.socket

由 旧街凉风 提交于 2020-04-16 03:20:32
问题 I've created image that use for jenkins agent slave Here it is: https://hub.docker.com/r/kondaurov/jenkins_agent/~/dockerfile/ Than i run it: docker run -d -p 2222:22 --name=jenkins_agent -v /var/run/docker.sock:/var/run/docker.sock -v kondaurov/jenkins_agent Then i create new node in jenkins and it connects successfully via ssh I try to run this pipeline: pipeline { agent { docker { label 'agent01' image 'hello-world' } } stages { stage('Compile') { steps { sh 'whoami' sh 'echo $PATH' } } }

Can you identify from inside a jenkins pipeline if its the first run of a new branch?

由 半城伤御伤魂 提交于 2020-04-16 02:38:07
问题 Is it possible to see if a pipeline job is the first run of a newly discovered branch from inside the pipeline itself? If you could get a list of all the runs of a job maybe you could see if there are 0 previous runs and thereby know its the first run? 回答1: Use env.BUILD_NUMBER . env.BUILD_NUMBER == '1' if this is the first build. For newly discovered branches in Multibranch Pipeline (which I assume you use) this will work. 回答2: In case you mean to identify the build number from within the

Jenkins 安装教程

由 99封情书 提交于 2020-04-15 14:47:06
【推荐阅读】微服务还能火多久？>>> 资源准备 https://jenkins.io/ https://tomcat.apache.org/download-80.cgi windows 平台 1 2 3 4 5 6 7 8 9 10 11 12 13 来源： oschina 链接： https://my.oschina.net/u/4368490/blog/3235566

解决jenkins无法正常安装一些插件

由 不羁岁月 提交于 2020-04-14 10:55:52
【推荐阅读】微服务还能火多久？>>> jenkins安装时会让你选择一些常用的插件而一些插件在安装的过程中由于缺少其他插件的依赖 所以会安装不成功。不要怕，找个所需要的插件直接去jenkins的插件库去搜索，手动下载出来。然后在手动上传，然后在重新去下载所需要的插件 即可。 1：复制依赖的插件 2：在插件库找到该插件 点击进入 3：点击下载自己所需要的版本 来源： oschina 链接： https://my.oschina.net/u/4417586/blog/3234091

jenkins 安装git插件的那些坑

由 限于喜欢 提交于 2020-04-14 08:58:51
【今日推荐】：为什么一到面试就懵逼！>>> jenkins 是无法直接按照git 插件的，因为git的一些依赖包jenkins是没有的。以下是我在解决jenkins安装git插件问题的处理步骤，亲测有效。 1：打开https://plugins.jenkins.io/ 搜索git 然后点击进入。 2：手动下载git需要的插件。git_client.hpi插件、scm-api.hpi插件、workflow-setp-api.hpi插件、workflow-scm-setp.hpi插件 3：然后去插件管理处上传已下载好的插件 ，在去重新下载git插件 即可。 来源： oschina 链接： https://my.oschina.net/u/4327212/blog/3233941

Jenkins Git plugin: git describe cannot describe anything

由 不想你离开。 提交于 2020-04-14 02:31:34
问题 I am using the Git Plugin of Jenkins ans use Douglas Creager's get_git_version script. This uses git describe to get some sensible version for python modules. Usually this creates something like 0.1-11-g80fe130 , but on jenkins I get: + git describe fatal: No names found, cannot describe anything. I have configured the plugin not to come up with its own tags through 'skip internal tags'. Doing an extra checkout of the master branch like in this question about pushing from jenkins doesn't help

Jenkins Git plugin: git describe cannot describe anything

由 别等时光非礼了梦想. 提交于 2020-04-14 02:28:08
问题 I am using the Git Plugin of Jenkins ans use Douglas Creager's get_git_version script. This uses git describe to get some sensible version for python modules. Usually this creates something like 0.1-11-g80fe130 , but on jenkins I get: + git describe fatal: No names found, cannot describe anything. I have configured the plugin not to come up with its own tags through 'skip internal tags'. Doing an extra checkout of the master branch like in this question about pushing from jenkins doesn't help

Jenkins 2.192: HTTP Error 403: No valid crumb was included in the request

由 ∥☆過路亽．° 提交于 2020-04-13 20:08:39
问题 I recently upgraded to Jenkins 2.192, and my applications started failing with the following error: HTTP Error 403: No valid crumb was included in the request Reason: No valid crumb was included in the request I do not see the problem after downgrading to Jenkins 2.189. I do not see the issue with Jenkins 2.189, 2.190, 2.191. I hit the issue with Jenkins 2.192 (also seen with 2.196) SOMETHING CHANGED BETWEEN 2.191 AND 2.192 , causing the failure I observed. 回答1: Refer - https://support

.Net微服务实践（四）[网关]：Ocelot限流熔断、缓存以及负载均衡

由 半城伤御伤魂 提交于 2020-04-13 13:46:36
【今日推荐】：为什么一到面试就懵逼！>>> 目录 限流 熔断 缓存 Header转化 HTTP方法转换 负载均衡 注入/重写中间件 后台管理 最后 在上篇 .Net微服务实践（三）[网关]：Ocelot配置路由和请求聚合 中我们介绍了Ocelot的配置，主要特性路由以及服务聚合。接下来，我们会介绍Ocelot的限流、熔断、缓存以及负载均衡。 限流 我们先来看限流的配置 Reroute节点中的配置如下： { "DownstreamPathTemplate": "/api/orders", "DownstreamScheme": "http", "DownstreamHostAndPorts": [ { "Host": "localhost", "Port": 5001 } ], "UpstreamPathTemplate": "/api/orders", "UpstreamHttpMethod": [ "Get" ], "RateLimitOptions": { "ClientWhitelist": [], "EnableRateLimiting": true, "Period": "10m", "PeriodTimespan": 3, "Limit": 1 } } GlobalConfiguration中的配置如下： "GlobalConfiguration": {
订阅 Jenkins