Jenkins

Jenkins: Git push will trigger a Jenkins build for only that branch

て烟熏妆下的殇ゞ 提交于 2021-02-08 05:43:22
问题 We are working in parallel on a number of Git branches. When pushing a specific Git branch, how can we start a Jenkins item/job that will trigger the build of that specific branch? As an example: we push a Git branch "feature-abc" ==> this should trigger a Jenkins build job using/pulling that branch "feature-abc". For each new feature we have a branch, so the number of branches is not fixed. So, I think it is different than this answer with a manual action. 回答1: If the use case is to trigger

SEVERE: https://jenkins.domainname.com/tcpSlaveAgentListener/ appears to be publishing an invalid X-Instance-Identity

本小妞迷上赌 提交于 2021-02-08 05:19:11
问题 We're trying to connect a previously connected agent to a Jenkins server. We get the following error: SEVERE: https://jenkins.domainname.com/tcpSlaveAgentListener/ appears to be publishing an invalid X-Instance-Identity. java.io.IOException: https://jenkins.domainname.com/tcpSlaveAgentListener/ appears to be publishing an invalid X-Instance-Identity. at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287) at hudson.remoting.Engine.innerRun(Engine

SEVERE: https://jenkins.domainname.com/tcpSlaveAgentListener/ appears to be publishing an invalid X-Instance-Identity

爱⌒轻易说出口 提交于 2021-02-08 05:19:03
问题 We're trying to connect a previously connected agent to a Jenkins server. We get the following error: SEVERE: https://jenkins.domainname.com/tcpSlaveAgentListener/ appears to be publishing an invalid X-Instance-Identity. java.io.IOException: https://jenkins.domainname.com/tcpSlaveAgentListener/ appears to be publishing an invalid X-Instance-Identity. at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287) at hudson.remoting.Engine.innerRun(Engine

Jenkins - get latest artifact with curl

杀马特。学长 韩版系。学妹 提交于 2021-02-08 05:11:28
问题 I've been looking around and cannot find how to download the latest artifact with curl or even just to know the link. I've discovered the permalinks and api xml/json feeds which contain all the data that is needed such as the artifact names etc....Also discovered the special link that zips all artifacts, but my artifact is already zipped. Is there is a way to not have to pick out information and just use a simple link. In other words, tell jenkins to give me the latest artifact of job x

Jenkins - get latest artifact with curl

不问归期 提交于 2021-02-08 05:10:18
问题 I've been looking around and cannot find how to download the latest artifact with curl or even just to know the link. I've discovered the permalinks and api xml/json feeds which contain all the data that is needed such as the artifact names etc....Also discovered the special link that zips all artifacts, but my artifact is already zipped. Is there is a way to not have to pick out information and just use a simple link. In other words, tell jenkins to give me the latest artifact of job x

Jenkins - get latest artifact with curl

試著忘記壹切 提交于 2021-02-08 05:07:49
问题 I've been looking around and cannot find how to download the latest artifact with curl or even just to know the link. I've discovered the permalinks and api xml/json feeds which contain all the data that is needed such as the artifact names etc....Also discovered the special link that zips all artifacts, but my artifact is already zipped. Is there is a way to not have to pick out information and just use a simple link. In other words, tell jenkins to give me the latest artifact of job x

Using Docker for Windows in Jenkins Declarative Pipeline

你说的曾经没有我的故事 提交于 2021-02-07 21:50:26
问题 I am setting up a CI workflow with Jenkins declarative pipeline and Docker-for-Windows agents through Dockerfile . Note: It is unfortunately currently not a solution to use a Linux-based docker daemon, since I need to run Windows binaries. Setup: Jenkins master runs on Linux 16.04 through Docker. Jenkins build agent is Windows 10 Enterprise 1709 (16299.551) Docker-for-Windows 17.12.0-ce Docker 18.x gave me headaches when trying to use Windows Containers, so I rolled back to 17.x. I still had

Using Docker for Windows in Jenkins Declarative Pipeline

…衆ロ難τιáo~ 提交于 2021-02-07 21:50:18
问题 I am setting up a CI workflow with Jenkins declarative pipeline and Docker-for-Windows agents through Dockerfile . Note: It is unfortunately currently not a solution to use a Linux-based docker daemon, since I need to run Windows binaries. Setup: Jenkins master runs on Linux 16.04 through Docker. Jenkins build agent is Windows 10 Enterprise 1709 (16299.551) Docker-for-Windows 17.12.0-ce Docker 18.x gave me headaches when trying to use Windows Containers, so I rolled back to 17.x. I still had

Difference between different jenkins pipeline plugin

柔情痞子 提交于 2021-02-07 17:55:01
问题 I am working on to setup regression for one of my project through jenkins. I am new to jenkins and kind of confused with so many available pipeline plugins. To name a few: Pipeline Plugin Build Pipeline Plugin Delivery Pipeline Plugin They all seem same to me. Can anyone help me decide when to use which plugin? Thanks. 回答1: While the idea is the same, they are very different in the way how you implement a deployment pipeline. Long story short: use the Pipeline plugin, which is the "new" way

Jenkins stapler requests fail with no valid crumb

女生的网名这么多〃 提交于 2021-02-07 14:44:38
问题 I'm working on a Jenkins plugin and I'm now stuck at a point where I'm trying to get the return value of a method using a JavaScript proxy as described here. I simply want to call this kotlin method: @JavaScriptMethod fun getMonitoredJobsAsJSON(): JSONArray = toJSON(getObjectMapper().writeValueAsString(getMonitoredJobs())) as JSONArray From the jelly script using this: <script> var board = <st:bind value="${it}"/> board.getMonitoredJobsAsJSON(function(data) { // }) </script> This actually