[JIRA] (JENKINS-58301) Kubernetes Plugin Repeated Socket Ping Timeout Exceptions
Title: Message Title Deiwin Sarjas commented on JENKINS-58301 Re: Kubernetes Plugin Repeated Socket Ping Timeout Exceptions We configured -Dkubernetes.websocket.ping.interval=3 for Jenkins based on this comment on another issue. I'll report back if it helps or not. 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.200367.1562076713000.177.1568800622149%40Atlassian.JIRA.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Deiwin Sarjas commented on JENKINS-58306 Re: Kubernetes plugin upgrade breaks ownerReference usage Thank you for the quick fix and release! 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.200414.1562098146000.13624.1563348900520%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title
Deiwin Sarjas commented on JENKINS-58306
Re: Kubernetes plugin upgrade breaks ownerReference usage
Here's a pipeline snippet that checks for this behavior. I left out the auth things, because they're specific to the k8s cluster. We use a default service account in some cases and a kubectl config mounted from a k8s secret in other cases, for reference.
def kubectlYaml = """\
apiVersion: v1
kind: Pod
spec:
containers:
- name: kubectl
image: bitnami/kubectl:1.12
stdin: true
tty: true
command:
- '/bin/sh'
args:
- -c
- cat
env:
- name: HUB_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: HUB_UID
valueFrom:
fieldRef:
fieldPath: metadata.uid
- name: HUB_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
securityContext:
runAsUser: 1000
fsGroup: 1000
"""
def name = "test-${UUID.randomUUID()}"
podTemplate(
cloud: '..',
name: name,
label: name,
podRetention: never(),
idleMinutes: 0,
yaml: kubectlYaml,
) {
node(name) {
container('kubectl') {
sh('''\
deploy=$(
kubectl create -o name -f -
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Deiwin Sarjas commented on JENKINS-58306 Re: Kubernetes plugin upgrade breaks ownerReference usage Just FYI, we use this to create on-deman Selenium clusters. The test pod has a container for the Selenium hub, and then we spawn a whole bunch of browsers. The browsers are garbage collected by k8s after the test finishes and the test pod is cleaned up by kubernetes-plugin. 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.200414.1562098146000.6940.1562768880497%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Deiwin Sarjas commented on JENKINS-58306 Re: Kubernetes plugin upgrade breaks ownerReference usage Yeah, I think I can put together a simple Jenkinsfile to demonstrate this. I'll post it here when I have one. 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.200414.1562098146000.6932.1562768701163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58306) Kubernetes plugin upgrade breaks ownerReference usage
Title: Message Title Deiwin Sarjas created an issue Jenkins / JENKINS-58306 Kubernetes plugin upgrade breaks ownerReference usage Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-07-02 20:09 Environment: Jenkins 2.176.1 kubernetes-plugin 1.16.2 Priority: Minor Reporter: Deiwin Sarjas Background We create Kubernetes resources (Deployments) from within Kubernetes Pods created with podTemplate. We want these resources to be deleted when the Pod created with podTemplate is deleted. To do this we set ownerReferences for the created resources, using the generated Pod's name and uid. This worked well for us a for a while. Problem We upgraded the Kubernetes plugin from 1.15.2 to 1.16.2 and this stopped working. The manually created resources (Deployments) weren't being cleaned up by Kubernetes garbage collection any more. We had to revert the plugin upgrade. Possible cause Version 1.16.0 of the plugin upgraded kubernetes-client from 4.1.3 to 4.3.0. The changelog for kubernetes-client includes only one change within that range that would be likely to cause this change in behavior: Fix #758: Deleting Deployments with `.cascading(true)` creates a new Replica Set. Possible fix I don't understand the plugin's code well, but it seems like adding .cascading(true) to this line could return the previous behavior.
[JIRA] (JENKINS-58301) Kubernetes Plugin Repeated Socket Ping Timeout Exceptions
Title: Message Title Deiwin Sarjas commented on JENKINS-58301 Re: Kubernetes Plugin Repeated Socket Ping Timeout Exceptions We've also been seeing quite a bit of this recently on EKS with Jenkins 2.164.2, Kubernetes plugin 1.15.2. 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.200367.1562076713000.215.1562096520169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44426) GitHub still triggering on SCM changes after polling option set to false
Title: Message Title Deiwin Sarjas commented on JENKINS-44426 Re: GitHub still triggering on SCM changes after polling option set to false It is still an issue. I'm using the following instead of poll: false as a workaround. It works, but it has the downside that all the repositories that use checkout have to be cloned to a workspace every time one of them is pushed to, even though none of them will actually trigger the build. extensions: [[$class: 'PathRestriction', includedRegions: '__nothing__']] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53518) Image variable does not uniquely identify an image
Title: Message Title
Deiwin Sarjas created an issue
Jenkins / JENKINS-53518
Image variable does not uniquely identify an image
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2018-09-12 08:48
Environment:
Jenkins ver. 2.121.3 Docker Pipeline 1.17
Priority:
Minor
Reporter:
Deiwin Sarjas
Summary The following code may push a completely unrelated image.
def image = docker.build('foo')
image.push('v0.0.1')
Explanation The plugin will store foo:latest as the identifier for that image variable, so that image.push will execute docker push foo:latest, for example. This has unexpected consequences in some situations. Examples follow. Scenario 1
Two separate jobs execute docker.build('foo') in parallel (using the same docker daemon)
Both jobs finish building the image before either pushes the image, with job #2 finishing last
Both jobs will now push the image built by job #2, although it may use completely different source for building the image than job #1
Scenario 2 We recently ran into this one. This is even worse than the first scenario, because there's no race condition here - no need to run multiple jobs with specific timings.
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Deiwin Sarjas commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value This is marked with a priority "Minor", which is defined as "Minor loss of function, or other problem where easy workaround is present.". Not being able to provision pods feels pretty major to me and as far as I can see there's no known workaround. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41162) Input descriptions can contain html tags - allow or prevent
Title: Message Title Deiwin Sarjas commented on JENKINS-41162 Re: Input descriptions can contain html tags - allow or prevent As far as I can tell, something similar is already supported in JENKINS-41769. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41162) Input descriptions can contain html tags - allow or prevent
Title: Message Title Deiwin Sarjas commented on JENKINS-41162 Re: Input descriptions can contain html tags - allow or prevent Would it be possible to re-enable safe HTML for the input descriptions? My use case is presenting a checklist with links to the user during an input step. E.g.: input(message: 'Continue? ', parameters: [ booleanParam( defaultValue: false, description: '"https://google.com">The project dashboard looks OK', name: 'dashboard' ), booleanParam( defaultValue: false, description: 'No new errors in "https://google.com">the project logs', name: 'logs' ) ]) In the old UI this works well: But in the new (which, granted, looks much better), the links are removed: This means I have to include the full link in the text and users have to copy paste that URL. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41162) Input descriptions can contain html tags - allow or prevent
Title: Message Title Deiwin Sarjas updated an issue Jenkins / JENKINS-41162 Input descriptions can contain html tags - allow or prevent Change By: Deiwin Sarjas Attachment: Screen Shot 2018-04-13 at 15.53.12.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41162) Input descriptions can contain html tags - allow or prevent
Title: Message Title Deiwin Sarjas updated an issue Jenkins / JENKINS-41162 Input descriptions can contain html tags - allow or prevent Change By: Deiwin Sarjas Attachment: Screen Shot 2018-04-13 at 15.53.02.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50312) Build hangs when invalid envVar key is used
Title: Message Title
Deiwin Sarjas created an issue
Jenkins / JENKINS-50312
Build hangs when invalid envVar key is used
Issue Type:
Improvement
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-03-21 10:04
Environment:
Jenkins ver. 2.89.4, Kubernetes plugin 1.3.2
Priority:
Minor
Reporter:
Deiwin Sarjas
Summary Specifying a containerTemplate with envVars: [envVar(key: 'test.key', value: 'value')] fails (on Kubernetes version <1.8) and user is not notified of the failure. Description I was trying to configure an environment variable with a dot (".") in the name (for Elasticsearch, where it's suggested in their documentation) for a containerTemplate, the job didn't fail but also didn't finish. It got stuck at provisioning a pod. Defining non-C-identifier env variable names did not work prior to Kubernetes version 1.8 and we're using 1.7, so it's expected that the pod creation fails. However, I'd expect the job to also fail and to see an informative error message in the job output. Currently, the job hangs with the following message:
Still waiting to schedule task
All nodes of label ‘pipeline-docker-build-1748220349’ are offline
When looking at the logs for the plugin, the following logs repeat multiple times, with different suffixes for the pod name:
Mar 21, 2018
