[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title Sergio Merino reopened an issue I am reopening the ticket because I am having this issue and He Bihong is right. You can change the max requests per host, but given that the default max requests is 64, there is no way of going over that Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Change By: Sergio Merino Resolution: Duplicate Status: Resolved Reopened Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59959) The Concurrency Limit is not always respected.
Title: Message Title Sergio Merino commented on JENKINS-59959 Re: The Concurrency Limit is not always respected. I have a similar problem. The plugin execute as much pods as possible whenever it is under the limit. And stop when it is over the limit. But doesn't start just the proper amount of pods to don't exceed the limit. Example: If the status is this: Pods Limit: 30 Running: 30 Queued: 50 As soon as one running pod finish, Jenkins is going to execute the 50 queued ones at the same time, so you will finish with: Pods Limit: 30 Running: 30 -1 (finished) + 50 = 79 Queued: 0 So, the limit is not respected at all I was expecting that the plugin can manage the internal queue, even running the pods in the correct order Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202763.1572257812000.6824.1580142300680%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title
Sergio Merino updated an issue
Jenkins / JENKINS-58789
Timestamps disappear without any reason inside podTemplate
Change By:
Sergio Merino
Comment:
As workaround, adding "timestamps{}" inside podTemplate works. But I was expecting, that configuring it at the higher level would be enough
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201099.1564764393000.9660.1565173380137%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title
Sergio Merino commented on JENKINS-58789
Re: Timestamps disappear without any reason inside podTemplate
As workaround, adding "timestamps{}" inside podTemplate works. But I was expecting, that configuring it at the higher level would be enough
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201099.1564764393000.6972.1564764480105%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title
Sergio Merino created an issue
Jenkins / JENKINS-58789
Timestamps disappear without any reason inside podTemplate
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-08-02 16:46
Priority:
Minor
Reporter:
Sergio Merino
I found this problem after updating from kubernetes:1.17.2 to kubernetes:1.18.1. The timestamp stop appearing for code running inside podTemplate. Not sure if this problem could be related with other plugins, but it is only happening inside podTemplate. Code to replicate the behavior:
timestamps{
Integer echoNumbers = 3
node("master") {
for (i = 0; i "echo \"Pre POD hello ${i}\" && sleep 1"
}
}
podTemplate(showRawYaml: false, label: "alpine1", cloud: "Build farm", containers: [
containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {
node ("alpine1") {
for (i = 0; i "echo \"POD hello ${i}\" && sleep 1"
}
}
}
node("master") {
for (i = 0; i "echo \"POST POD hello ${i}\" && sleep 1"
}
}
}
Console log:
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] timestamps
[Pipeline] {
[Pipeline] node
17:44:27 Running on Jenkins in /var/jenkins_home/jobs/***/workspace
[Pipeline] {
[Pipeline] sh
17:44:27 + echo Pre POD hello 0
17:44:27 Pre POD hello 0
17:44:27 + sleep 1
[Pipeline] sh
17:44:28 + echo Pre POD hello 1
17:44:28 Pre POD hello 1
17:44:28
[JIRA] (JENKINS-58709) Nested pod templates inherit container of upper level pod
Title: Message Title
Sergio Merino updated an issue
Jenkins / JENKINS-58709
Nested pod templates inherit container of upper level pod
Change By:
Sergio Merino
kubernetes plugin version: 1.17.2When I run a podTemplate nested, it inherit the containers of the upper level podTemplate. It is a weird behaviour is better to explain it with an exampleCode:{code:java}podTemplate(showRawYaml: true, label: "alpine1", cloud: "Build farm", containers: [ containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {node ("alpine1") {container('alpine') {sh 'whoami'podTemplate(showRawYaml: true, label: "golang", cloud: "Build farm", containers: [ containerTemplate(name: 'golang', image: 'golang', ttyEnabled: true, command: "cat")]) { node ("golang") {container('golang') { sh 'sleep 120'} }}}}} {code} Expected * alpine pod template containers: \{jnlp} \{alpine} * golang pod template containers: \{jnlp} \{golang}What I have: * alpine pod template containers: \{jnlp} \{alpine} * golang pod template containers: \{jnlp} \{golang} \{alpine} Log(removed env variables):{code:java} Still waiting to schedule taskWaiting for next available executor on 'alpine1-dgpx2-5jp6k'Agent alpine1-prfs1-ghwvg is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata: annotations:buildUrl: "https:// callisto . dev . youview . co.uk/job/CII_test_pod_template_nest/13/ " labels:jenkins: "slave"jenkins/alpine1: "true" name: "alpine1-prfs1-ghwvg"spec: containers: - command:- "cat"env:- name: "JENKINS_SECRET" ...image: "alpine"imagePullPolicy: "IfNotPresent"name: "alpine"resources: limits: {} requests: {}securityContext: privileged: falsetty: truevolumeMounts:- mountPath: "/home/jenkins" name: "workspace-volume" readOnly: falseworkingDir: "/home/jenkins" - env:- name: "JENKINS_SECRET" ...image: "jenkins/jnlp-slave:alpine"name: "jnlp"volumeMounts:- mountPath: "/home/jenkins" name: "workspace-volume" readOnly: false nodeSelector: {} restartPolicy: "Never" volumes: - emptyDir: {}name: "workspace-volume"Running on alpine1-prfs1-ghwvg in /home/jenkins/workspace/CII_test_pod_template_nest[Pipeline] {[Pipeline] container[Pipeline] {[Pipeline] sh+ whoamiroot[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeStill waiting to schedule task'golang-t6g4f-4tzqr' is offlineAgent golang-t6g4f-4tzqr is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata: annotations:buildUrl: "https:// callisto . dev . youview . co.uk/job/CII_test_pod_template_nest/13/ " labels:jenkins: "slave"jenkins/golang: "true" name: "golang-t6g4f-4tzqr"spec: containers: - command:- "cat"env:- name: "JENKINS_SECRET" ...image: "alpine"imagePullPolicy:
[JIRA] (JENKINS-58709) Nested pod templates inherit container of upper level pod
Title: Message Title
Sergio Merino created an issue
Jenkins / JENKINS-58709
Nested pod templates inherit container of upper level pod
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-07-29 14:11
Priority:
Minor
Reporter:
Sergio Merino
kubernetes plugin version: 1.17.2 When I run a podTemplate nested, it inherit the containers of the upper level podTemplate. It is a weird behaviour is better to explain it with an example Code:
podTemplate(showRawYaml: true, label: "alpine1", cloud: "Build farm", containers: [
containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {
node ("alpine1") {
container('alpine') {
sh 'whoami'
podTemplate(showRawYaml: true, label: "golang", cloud: "Build farm", containers: [
containerTemplate(name: 'golang', image: 'golang', ttyEnabled: true, command: "cat")]) {
node ("golang") {
container('golang') {
sh 'sleep 120'
}
}
}
}
}
}
Expected
alpine pod template containers: {jnlp} {alpine}
golang pod template containers: {jnlp} {golang}
What I have:
alpine pod template containers: {jnlp} {alpine}
golang pod template
[JIRA] (JENKINS-58574) showRawYaml parameter doesn't work for nested podTemplates
Title: Message Title
Sergio Merino created an issue
Jenkins / JENKINS-58574
showRawYaml parameter doesn't work for nested podTemplates
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-07-19 17:20
Priority:
Minor
Reporter:
Sergio Merino
kubernetes plugin version: 1.17.2 With a normal podTemplate I can set showRawYaml to false to don't show the YAML, but if I nest it, the second podTemplate show the YAML whether I set showRawYaml to false or not I have tested it in a pipeline job with this code:
podTemplate(showRawYaml: false, label: "alpine1", cloud: "Build farm", containers: [
containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {
node ("alpine1") {
container('alpine') {
sh 'whoami'
podTemplate(showRawYaml: false, label: "alpine2", cloud: "Build farm", containers: [
containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {
node ("alpine2") {
container('alpine') {
sh 'whoami'
}
}
}
}
}
}
[JIRA] (JENKINS-53361) Copy files using a regular expresion
Title: Message Title Sergio Merino created an issue Jenkins / JENKINS-53361 Copy files using a regular expresion Issue Type: Improvement Assignee: Naresh Rayapati Components: ssh-steps-plugin Created: 2018-08-31 08:47 Priority: Minor Reporter: Sergio Merino Sometime it is needed to copy more than one file, for example, xml files contained on a directory. The equivalent of: scp my_dir/*.xml user@server:output_directory/ I think not be able to copy more than one file at once is a limitation Add Comment
[JIRA] [gitlab-hook-plugin] (JENKINS-32745) Plugin don't work using a variable in the repository url
Title: Message Title
Sergio Merino created an issue
Jenkins / JENKINS-32745
Plugin don't work using a variable in the repository url
Issue Type:
Bug
Assignee:
Javier Palacios
Components:
gitlab-hook-plugin
Created:
03/Feb/16 10:28 AM
Environment:
Jenkins ver. 1.646 Gitlab hook plugin 1.4.1.1
Priority:
Minor
Reporter:
Sergio Merino
Add in configuration a environment called: GIT_REPO with value github.com At a job configure the git repository like this: git@$ {GIT_REPO}
:/jenkinsci/gitlab-hook-plugin.git
Using normal git polling system works but not the gitlab hook plugin. At the log it shows there are not matching projects
Add Comment
