[JIRA] (JENKINS-60088) Change pod label - build label from unique key to value.
Title: Message Title Matthew Ludlum created an issue Jenkins / JENKINS-60088 Change pod label - build label from unique key to value. Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2019-11-07 15:43 Priority: Minor Reporter: Matthew Ludlum We combine filebeat with kubernetes to parse out container logs for the build system. SInce the plugin uses a unique key value for each build, you can quickly exceed the default 10,000 fields limit for builds. Filebeat does not currently offer a regex to drop matching fields so we can't drop the single label matching our build label from being parsed. https://github.com/elastic/beats/issues/12923 Since there is little value in keeping this as a unique key but instead should move to using a single key name with a value. Add Comment
[JIRA] (JENKINS-46003) Restrict ability to allow privileged containers to only exist in System Configuration
Title: Message Title Matthew Ludlum commented on JENKINS-46003 Re: Restrict ability to allow privileged containers to only exist in System Configuration Revisiting this ticket as much as changed but still not much. A better idea behind this might be to define how a mutating web controller in the kubernetes space can interact with the plugin or at least it's scheduling to help provide this implementation. 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.184227.1501879195000.13170.1563306480241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed The ping setting is only settable via parameter when starting jenkins as of right now, per my reading through the source and docs. 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum edited a comment on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ***setting the timeout will probably not fix the ping issue***To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release.[https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82]Starting with okhttp 3.10([https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100|https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100] )- it started aggressively checking connectivity with the pingInterval as well.To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. The okhttp docs recommend 30s : bq. If you have a configured ping interval, you should confirm that it is long enough for a roundtrip from client to server. If your ping interval is too short, slow connections may be misinterpreted as failed connections. A ping interval of 30 seconds is reasonable for most use cases. 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum edited a comment on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ***setting the timeout will probably not fix the ping issue***To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release.[https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82]Starting with okhttp 3.10([https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100|https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100 ) ] )- it started aggressively checking connectivity with the pingInterval as well.To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum edited a comment on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ***setting the timeout will probably not fix the ping issue***To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release. [https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82]Starting with okhttp 3.10([https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100 |https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100 )] ) - it started aggressively checking connectivity with the pingInterval as well.To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed **setting the timeout will probably not fix the ping issue** To confirm, this is likely an issue with updating to the latest fabric8 client, which went from 3.9.1 to 3.12.0 of okhttp as of the latest release. https://github.com/fabric8io/kubernetes-client/commit/9a40df1346876764fecf1cc170f482cc3722cd7a#diff-600376dffeb79835ede4a0b285078036L82 Starting with okhttp 3.10(https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-3100) - it started aggressively checking connectivity with the pingInterval as well. To fix this, adding -Dkubernetes.websocket.ping.interval= to the jenkins startup or system file should change the ping interval. 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-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Matthew Ludlum commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed I'm guessing a change in the fabric8 client 4.1.2 upgrade which included okHttp 3.12.0 caused this regression to pop up in 1.14.8 vs . prior versions. 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-56133) Embed build url of calling job into pod annotations
Title: Message Title Matthew Ludlum created an issue Jenkins / JENKINS-56133 Embed build url of calling job into pod annotations Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-02-13 20:42 Priority: Minor Reporter: Matthew Ludlum Due to how pod names are constructed and can be freely designed, it is often difficult to tie any single pod back to a build. This is important to do in some cases, such as tracking down the owner of pod, determine the resource usage of a build, or provide feedback if the pod uses non-pullable images. To that end, adding an annotation for the full build URL to the pod metadata will allow us to quickly identify the build server and build responsible for that pod. Add Comment
[JIRA] (JENKINS-51273) Inconsistent Declarative Behavior in Yaml File vs legacy podTemplate
Title: Message Title Matthew Ludlum stopped work on JENKINS-51273 Change By: Matthew Ludlum Status: In Progress Open 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-51273) Inconsistent Declarative Behavior in Yaml File vs legacy podTemplate
Title: Message Title Matthew Ludlum created an issue Jenkins / JENKINS-51273 Inconsistent Declarative Behavior in Yaml File vs legacy podTemplate Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-05-11 18:05 Priority: Major Reporter: Matthew Ludlum Depending on the type of declarative pipeline, you can experience inconsistent behavior and inheritance of variables. Using the SSH Agent example, you can see that the container and sshAgent wrappers do not always play nice. https://github.com/MattLud/kubernetes-plugin/commit/3488e1ff1e7d5195616883a9a18dcd593ba29397 The take away is that using the legacy pod template WITH declarative pipeline is the only one that works. The rest, declarative and fromYaml with declarative and declarative pipeline, fail to work inside the sshAgent block. Add Comment
[JIRA] (JENKINS-49370) Environment variables cannot be set within the container step
Title: Message Title Matthew Ludlum commented on JENKINS-49370 Re: Environment variables cannot be set within the container step This issue may be resolved with JENKINS-42582. 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-42582) ssh-agent not applied in kubernetes container
Title: Message Title Matthew Ludlum started work on JENKINS-42582 Change By: Matthew Ludlum Status: Reopened In Progress 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-42582) ssh-agent not applied in kubernetes container
Title: Message Title Matthew Ludlum commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container I think I have found a solution for this - we can use override the computer getEnvironment to drop the computer level properties(JAVA_HOME, etc) and use the built in variables without issue. This would avoid the need for workarounds. 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-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Matthew Ludlum commented on JENKINS-48490 Re: Intermittently slow docker provisioning with no errors I've been trying to reproduce this issue on my local box using SSH executors with both 1.1.2 and 1.1.3 to no avail. We are still seeing it on other instances. In the short term, I've thrown together a quick and dirty script job to "unstick" the jobs. https://gist.github.com/MattLud/1f8a56fcce933f7e97c366de54c85ba9 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-49465) Build Environment Variables not available within Container Step
Title: Message Title
Matthew Ludlum commented on JENKINS-49465
Re: Build Environment Variables not available within Container Step
An example build would be this:
pipeline {
agent {
kubernetes{
label 'openjdk'
containerTemplate{
name 'openjdk'
image 'openjdk'
workingDir '/home/jenkins'
ttyEnabled true
command 'cat'
args ''
}
}
}
stages{
stage('Build') {
steps {
sh 'echo DEFAULT_BUILD_NUMBER: ${BUILD_NUMBER}'
container('jnlp')
{
sh 'echo JNLP_BUILD_NUMBER: ${BUILD_NUMBER}'
}
container('openjdk'){
sh 'echo OPENJDK_BUILD_NUMBER: ${BUILD_NUMBER}'
}
}
}
}
}
Where the container steps do not show the BUILD NUMBER.
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
[JIRA] (JENKINS-49465) Build Environment Variables not available within Container Step
Title: Message Title
Matthew Ludlum created an issue
Jenkins / JENKINS-49465
Build Environment Variables not available within Container Step
Issue Type:
Bug
Assignee:
Matthew Ludlum
Components:
kubernetes-plugin
Created:
2018-02-08 20:06
Priority:
Major
Reporter:
Matthew Ludlum
Currently, inside the build container steps, shell executions cannot access build-level parameters, such as SCM properties or Build information like BUILD_NUMBER. A workaround to allow this is to redeclare it: environment{ BUILD_NUMBER = "${BUILD_NUMBER} } But this should be fixed to allow smoother use of the Kubernetes Plugin
Add Comment
