On 29.05.2017 17:31, Stephen Connolly wrote:
[snip]
The ping is an application level ping, i.e. it submits a command into
the command queue and waits for the response to be generated.
The command channel can be functioning, but if there is a backlog in the
command queue on either side and the co
On 29.05.2017 17:02, Kristian wrote:
Did you already looked at
https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread ?
No, thank you. I didn't realize that the ping caused the connection loss
until yesterday (I am not a Java developer so I missed that)
Unfortunately: If I execute the line
Hi, I need access to a Jenkins variable that defines the user who started
the build.
It is essential for my usecase because i need to pass it to capistrano and
newrelic, in order to log who did it.
I stumbled upon the Build User Vars Plugin[1], but it appears that it
doesn't work, i can't seem
Same issue here. Our incremental builds suffer from very poor locality
because the pipeline *always* start on a completely different set of node
then last time, and we have quite a few nodes. I came up with the same
tricks you mention, but it did not help much. Did you find a better
solution al
I am trying to create a new job by triggering the jenkins' createItem
endpoint, using the following code:
$(document).ready(function() {
$("#create").click(function (e) {
e.preventDefault();
var newJobName = $("#jobname").val();
//console.log(newJobName);
jQ
On 29 May 2017 at 06:47, Andreas Tscharner wrote:
> On 22.05.2017 10:13, Andreas Tscharner wrote:
>
>> Hello World,
>>
>>
> Hello again,
>
> [snip]
>
>> FATAL: Befehlsausführung fehlgeschlagen
>> java.io.IOException: Backing channel 'JNLP4-connect connection from
>> build-vm1/192.168.168.160:1033
Did you already looked at
https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread ?
2017-05-29 15:47 GMT+02:00 Andreas Tscharner :
> On 22.05.2017 10:13, Andreas Tscharner wrote:
>>
>> Hello World,
>>
>
> Hello again,
>
> [snip]
>>
>> FATAL: Befehlsausführung fehlgeschlagen
>> java.io.IOException:
Hi Philippe,
As Carlos pointed out, have you already gone through the documentation on
the kubernetes-plugin: https://github.com/jenkinsci/kubernetes-plugin ?
What is shown there is enough to get you to a working state.
The section in that doc about *Pod template inheritance* is a bit
unclear/i
On 22.05.2017 10:13, Andreas Tscharner wrote:
Hello World,
Hello again,
[snip]
FATAL: Befehlsausführung fehlgeschlagen
java.io.IOException: Backing channel 'JNLP4-connect connection from
build-vm1/192.168.168.160:1033' is disconnected.
[snip]
I have found some more information in /var/log/
Hi all,
I am getting following while trying to release a test project using jenkins
artifactory plugin at "Artifactory release staging" step : (the
"Artifactory release staging" UI shows a red line on top)
16:54:17 ERROR: Processing failed due to a bug in the code. Please report
this to jenkin
Hi all,
I am getting following error while trying to release my project using
jenkins artifactory plugin: Jenkins version : 2.7.2, Artifactory plugin
version : 2.11.0
*16:54:17* ERROR: Processing failed due to a bug in the code. Please report
this to jenkinsci-users@googlegroups.com*16:54:17*
On 22.05.2017 10:13, Andreas Tscharner wrote:
Hello World,
[snip]
FATAL: Befehlsausführung fehlgeschlagen
java.io.IOException: Backing channel 'JNLP4-connect connection from
build-vm1/192.168.168.160:1033' is disconnected.
No-one? No idea?
Or any pointer to a similar (old)er issue?
TIA and
Hello World,
Our setup:
* Debian Linux 8 with Jenkins 2.32.2
* libvirt plugin for Jenkins
* 8 virtual machines (QEMU/KVM) running Windows 7
These 8 virtual machines are included as Jenkins nodes and contain 1
executors each.
In the configuration we have:
* Revert Snapshot to our initial setup
13 matches
Mail list logo
