[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title Daniel Watrous commented on JENKINS-57396 Re: Pods Terminate before container image can download Carlos Sanchez Thanks for the reply. Sorry I didn't notice that. I was looking for something in the settings, but it makes sense to put it in the podTemplate. 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.199178.1557479229000.359.1557841920338%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title Daniel Watrous resolved as Not A Defect Jenkins / JENKINS-57396 Pods Terminate before container image can download Change By: Daniel Watrous Status: Open Resolved Resolution: Not A Defect 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.199178.1557479229000.361.1557841920364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title
Daniel Watrous updated an issue
Jenkins / JENKINS-57396
Pods Terminate before container image can download
Change By:
Daniel Watrous
I have a build that uses 9 containers, but the Pod never gets to start because it can't finish downloading in the amount of time (100 seconds) that the kubernetes plugin allows.{code:java}io.fabric8.kubernetes.client.KubernetesClientTimeoutException: Timed out waiting for [10] milliseconds for [Pod] with name:[api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191] in namespace [jenkins]. at org.csanchez.jenkins.plugins.kubernetes.AllContainersRunningPodWatcher.await(AllContainersRunningPodWatcher.java:134) at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:128) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)May 10, 2019 8:57:17 AM FINER org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncherRemoving Jenkins node: api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191May 10, 2019 8:57:17 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminateTerminating Kubernetes instance for agent api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191May 10, 2019 8:57:17 AM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloudBuilding connection to Kubernetes k8s-houston URL https://api.eng. houston company . trinet-k8s. com: 7443 6443 / namespace jenkinsMay 10, 2019 8:57:17 AM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloudConnected to Kubernetes k8s-houston URL https://api.eng. houston company . trinet-k8s. com: 7443 6443 /May 10, 2019 8:57:17 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave deleteSlavePodTerminated Kubernetes instance for agent jenkins/api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191May 10, 2019 8:57:17 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminateDisconnected computer api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191{code}I would like to be able to set this in the settings, or at least as an argument when I start Jenkins.
[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title Daniel Watrous created an issue Jenkins / JENKINS-57396 Pods Terminate before container image can download Issue Type: Bug Assignee: Guillermo Sanchez Urien Components: kubernetes-ci-plugin Created: 2019-05-10 09:07 Environment: Jenkins 1.164.2, Kubernetes 1.14 Labels: jenkins kuberenetes-plugin Priority: Major Reporter: Daniel Watrous I have a build that uses 9 containers, but the Pod never gets to start because it can't finish downloading in the amount of time (100 seconds) that the kubernetes plugin allows. io.fabric8.kubernetes.client.KubernetesClientTimeoutException: Timed out waiting for [10] milliseconds for [Pod] with name:[api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191] in namespace [jenkins]. at org.csanchez.jenkins.plugins.kubernetes.AllContainersRunningPodWatcher.await(AllContainersRunningPodWatcher.java:134) at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:128) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title Daniel Watrous commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed Matthew Ludlum Are you suggesting that this might be better moved out of the plugin and handled by passing in a parameter when starting Jenkins? My other question is: Does the current connectTimeout value set that 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 Daniel Watrous commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed I created PR https://github.com/jenkinsci/kubernetes-plugin/pull/442 to fix the issue of these always reverting to zero. 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-56400) Pods left in Error state when slave-master communication fails
Title: Message Title Daniel Watrous commented on JENKINS-56400 Re: Pods left in Error state when slave-master communication fails Carlos Sanchez Sorry for the duplicate in this case. I probably should have added these details to the other thread, since it shows one way to reproduce the behavior. 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-54540) Pods stuck in error state is not cleaned up
Title: Message Title Daniel Watrous commented on JENKINS-54540 Re: Pods stuck in error state is not cleaned up podRetention is set to never. 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-56400) Pods left in Error state when slave-master communication fails
Title: Message Title
Daniel Watrous created an issue
Jenkins / JENKINS-56400
Pods left in Error state when slave-master communication fails
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
jenkins-bad-tunnel.png
Components:
kubernetes-plugin
Created:
2019-03-04 21:41
Environment:
Jenkins 1.50.3, kubernetes plugin 1.14.8
Priority:
Major
Reporter:
Daniel Watrous
When communication between the JNLP slave and the Jenkins master fails, Pods are left in an Error state, and in some cases require manual intervention to clean up. Non-JNLP containers are left running and consuming resources in kubernetes. Expected behavior would be to:
Fail the job if a suitable Pod can't be started to run the build
Make sure that any unsuccessful Pods are cleaned up by the kubernetes plugin
One way to reproduce this issue is by changing the Jenkins tunnel value to something invalid. This issue also happens even when the Jenkins tunnel reference is correct... When a job is run, the Console will show that it is waiting for a node
Started by user Admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] podTemplate
[Pipeline] {
[JIRA] (JENKINS-56396) A pipeline with a bad containerTemplate does not fail
Title: Message Title
Daniel Watrous created an issue
Jenkins / JENKINS-56396
A pipeline with a bad containerTemplate does not fail
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-03-04 20:26
Environment:
Jenkins 1.50.3, kubernetes plugin 1.14.8
Priority:
Major
Reporter:
Daniel Watrous
If a pipeline has a bad containerTemplate definition, the build won't fail, but will infinitely try to complete. The build job effectively hangs. Expected behavior would be to have the job fail if a Pod can be created for the build. Reproduce the issue with the following pipeline (notice the bad image reference):
def label = "mypod-${UUID.randomUUID().toString()}"podTemplate(cloud: 'k8s-dc1', label: label,
containers: [
containerTemplate(name: 'alpine', image: 'fakeimage', alwaysPullImage: false, ttyEnabled: true, command: 'cat')
]
)
{ node(label) {
stage('alpine') {
container('alpine') {
sh "pwd && ls -la"
}
}
}
}
In my environment, most users don't have access to the namespace where build pods are created, and there is no feedback to the user in Jenkins that there is a bad containerTemplate. When I run the build above, I see this in my build job, which only shows that it is waiting on the Pod (node) to become available.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Carlos Sanchez I'm confused by the version number you mention, 4.1.8. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I just checked both of those builds and they both failed for this same reason. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I'm still not completely sure how to get the exact logs you want, but I ran into this issue again yesterday and grabbed all the logs that were available at the time. They are attached. If you need something else, please provide more instructions. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous updated an issue Jenkins / JENKINS-55392 java.util.concurrent.RejectedExecutionException AGAIN Change By: Daniel Watrous Attachment: connection-error-log.txt 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I do see this repeating message, but I'm not sure it's related. Started Purge expired KubernetesClients Jan 17, 2019 4:42:17 PM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider gracefulClose Not closing io.fabric8.kubernetes.client.DefaultKubernetesClient@6f6f5e02: there are still running (10) or queued (0) calls Jan 17, 2019 4:42:17 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$PurgeExpiredKubernetesClients Finished Purge expired KubernetesClients. 3 ms Jan 17, 2019 4:43:17 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$PurgeExpiredKubernetesClients Started Purge expired KubernetesClients Jan 17, 2019 4:43:17 PM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider gracefulClose Not closing io.fabric8.kubernetes.client.DefaultKubernetesClient@6f6f5e02: there are still running (10) or queued (0) calls Jan 17, 2019 4:43:17 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$PurgeExpiredKubernetesClients Finished Purge expired KubernetesClients. 1 ms Jan 17, 2019 4:44:17 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$PurgeExpiredKubernetesClients 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I added the logger, but the Jenkins webui only keeps the last few hundred lines, so sometimes I can't copy and paste all the logs before they are gone. Is there some better way to capture these logs? From what I see so far, I don't see any logs about "force close", or "force" anything. I also don't see any logs that say "Removing entry", which it seems should be in the log you linked to. I'm not sure if I'm doing this right, so I may need more instructions. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Nevermind that last question. I get it now that you're asking about the Jenkins master. I'll gather some logs today and attach them to this issue. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title
Daniel Watrous commented on JENKINS-55392
Re: java.util.concurrent.RejectedExecutionException AGAIN
Jenkins ver. 2.150.1 with kubernetes plugin 1.14.3 / # kubectl version Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} We self-host on openstack in our datacenter. Kubernetes is deployed on CentOS7 using kubespray. When you say "master logs" do you mean the apiserver logs?
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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Carlos Sanchez Since you have reproduced this, do you still need the log data you mentioned in a previous post? I just read the notes in the PR you linked to above. In my case, we run out of connections when there is only one build Pod in some cases. This seems to suggest that there are lots of pending "exec" calls against Pods that no longer exist. Can they all just be deleted when the Pod is cleaned up at the end of a build? 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Marky Jackson I'm happy to help track this down, if you give me some pointers on how and where to look. Let me know if I can be helpful on this issue. I'm just not really sure where to start. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I attached a segment with all the calls related to a failed build that showed this error. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous updated an issue Jenkins / JENKINS-55392 java.util.concurrent.RejectedExecutionException AGAIN Change By: Daniel Watrous Attachment: kube-apiserver-k8s-master-0.app-ui-build-common-27bd2dc4.txt 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I have now increased my max connections to 512, but I'm confused about what they are. I get this error when there is only one build pod running with nine containers. The kubernetes API is obviously not saturated, so I don't think this really means connections to the kubernetes API. It seems like a leak scenario, where unused "connections" are not being returned to the pool. Is this like "kubectl exec..." connections? 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-42643) Conditional application of triggers in Declarative
Title: Message Title Daniel Watrous commented on JENKINS-42643 Re: Conditional application of triggers in Declarative Sean Grider, I found https://plugins.jenkins.io/parameterized-scheduler while looking for this same feature. My use case is a little different. I have a build that deploys software, but I want that software to get cleaned up some fixed number of hours after the last build. What I really want is to schedule a one time build, but I realized I might be able to use triggers for this. When the initial build runs, I dynamically generate the cron to run at a time that would be the number of hours later that I want. When the clean up build runs, I would set the cron trigger to an empty string, so it effectively on runs one time... 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-49794) BooleanParam default value is always true
Title: Message Title Daniel Watrous commented on JENKINS-49794 Re: BooleanParam default value is always true I also tried going in to the config.xml for that job and manually removing the parameters myParameter Set to true if you want to live true They were rewritten with the updated default value, but the build still ignores the default value and uses whatever the parameters were for that last build. I can't find a workaround other than committing this file into the repository and using "build with parameters", which isn't really a workaround. I guess another workaround would be to just change everywhere in the Jenkinsfile that references the parameter to the desired boolean value. It's not really testing what you plan to commit, but it simulates the desired behavior. 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-49794) BooleanParam default value is always true
Title: Message Title Daniel Watrous commented on JENKINS-49794 Re: BooleanParam default value is always true The way I use the Replay feature is to work through changes to my Jenkinsfile without committing a bunch of intermediate changes that may or may not work. I think the best way to "improve" this would be to add the parameters to the top of the replay page, as if I had clicked "build with parameters". I thought a workaround might be to go into the configuration of that pipeline and either delete the parameter or change its value. In my case, the pipeline is part of a multibranch pipeline and doesn't allow me to save changes to the pipeline. If this isn't a feature, there should at least be a workaround... 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-54540) Pods stuck in error state
Title: Message Title
Daniel Watrous created an issue
Jenkins / JENKINS-54540
Pods stuck in error state
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
build-job-console-output.txt, jnlp-container-log-error.txt, jnlp-container-log-healthy.txt
Components:
kubernetes-plugin
Created:
2018-11-08 12:10
Environment:
I am running Jenkins in kubernetes with the kubernetes plugin. Versions as follows ~ # kubectl version Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} Jenkins ver. 2.138.2 from https://hub.docker.com/r/jenkins/jenkins/ [centos@k8s-master-0 ~]$ sudo docker version Client: Version: 17.03.2-ce API version: 1.27 Go version: go1.7.5 Git commit: f5ec1e2 Built: Tue Jun 27 02:21:36 2017 OS/Arch: linux/amd64 Server: Version: 17.03.2-ce API version: 1.27 (minimum version 1.12) Go version: go1.7.5 Git commit: f5ec1e2 Built: Tue Jun 27 02:21:36 2017 OS/Arch: linux/amd64 Experimental: false
Labels:
jenkins kuberenetes-plugin kuberentes jnlp-slave jnlp plugin
Priority:
Minor
Reporter:
Daniel Watrous
[JIRA] (JENKINS-50749) SAMLException: No valid subject assertion found in response (Azure)
Title: Message Title Daniel Watrous commented on JENKINS-50749 Re: SAMLException: No valid subject assertion found in response (Azure) Ivan, I'm glad this was helpful. I was in the process of transitioning to https://plugins.jenkins.io/azure-ad as an alternative to this plugin, but depending on your timeline for submitting a fix, I'm willing to hold off on my transition and help you test any changes. I'm also willing to help with the fix if you give me some pointers about where to start looking in the code. 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-50749) SAMLException: No valid subject assertion found in response (Azure)
Title: Message Title Daniel Watrous created an issue Jenkins / JENKINS-50749 SAMLException: No valid subject assertion found in response (Azure) Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: saml-logs.txt Components: saml-plugin Created: 2018-04-11 19:05 Environment: Docker image jenkins/jenkins:2.107.1 (similar behavior in previous tagged versions too) deployed on kuberntes. SAML Plugin 1.0.5 Labels: jenkins SAML SAMLException Priority: Minor Reporter: Daniel Watrous I have used the saml-plugin to integrate our login with Azure Active Directory. This works most of the time, but sometimes (a few times a month) I get redirected to /securityRealm/finishLogin and I see the stacktrace shown below. I have attached logs to this ticket for org.pac4j.saml I have followed this ticket, https://issues.jenkins-ci.org/browse/JENKINS-44992. My configuration includes the IdP metadata URL and a Refresh Period of 120. I have extended my Maximum Authentication Lifetime to 1209600, which seems to make this happen less often. Sometimes I can workaround this by
[JIRA] (JENKINS-44992) SamlException after metadata update
Title: Message Title Daniel Watrous commented on JENKINS-44992 Re: SamlException after metadata update I am also running 1.0.5 and provided the IdP URL provided. I also still regularly get this error. Should I submit a new issue, since this one list listed as resolved? When it happens the user has to go to office365, logout and then revisit the Jenkins server and login again. 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.
