[JIRA] (JENKINS-41810) Timing issue with pid file population with bourne shell
Title: Message Title Gabe Montero created an issue Jenkins / JENKINS-41810 Timing issue with pid file population with bourne shell Issue Type: Task Assignee: Unassigned Components: durable-task-plugin Created: 2017/Feb/07 3:08 PM Environment: See with both jenkins v1.651.3 and v2.19.3, installed via rpm jdk - open jdk 1.8 x86_64 arch OS - centos 7 durable task plugin version - v1.12 Priority: Minor Reporter: Gabe Montero See https://github.com/jenkinsci/durable-task-plugin/pull/37 for details and proposed solution. Add Comment
[JIRA] (JENKINS-41810) Timing issue with pid file population with bourne shell
Title: Message Title Gabe Montero commented on JENKINS-41810 Re: Timing issue with pid file population with bourne shell Does seem similar to https://issues.jenkins-ci.org/browse/JENKINS-28400 , but just at a different spot in the flow / code (creation vs. exit). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41810) Timing issue with pid file population with bourne shell
Title: Message Title Gabe Montero updated an issue Jenkins / JENKINS-41810 Timing issue with pid file population with bourne shell Change By: Gabe Montero Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Gabe Montero closed an issue as Fixed Jenkins / JENKINS-48079 jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Change By: Gabe Montero Status: Resolved Closed 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-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Gabe Montero resolved as Fixed Commit 8f2239062cc5eeed9ccd1fc2be62832e2190e8b0 and v1.0.3 of the plugin provided the resolution for this issue. Jenkins / JENKINS-48079 jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Change By: Gabe Montero Status: Open Resolved Resolution: Fixed 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+unsubs
[JIRA] (JENKINS-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Gabe Montero commented on JENKINS-48079 Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Did you explicitly configure it from the Jenkins console. That is the "fix" 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-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title
Gabe Montero edited a comment on JENKINS-48079
Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Sorry, I got this bug confused with another one.I refreshed my memory with this and [https://bugzilla.redhat.com/show_bug.cgi?id=1510908]Yeah, there was no explicit intention to set the value in the jenkins.model.JenkinsLocationConfiguration.xml file from this pluginWe did not want to override an settings the user might have made to that file via Jenkins configuration.or the jenkins service in OpenShift. I'll also not not3 what jenkins.Model.Jenkins.getRootUrl() does: public @Nullable String getRootUrl() \{ String url = ""> if(url!=null) \{ return Util.ensureEndsWith(url,"/"); } StaplerRequest req = Stapler.getCurrentRequest(); if(req!=null) return getRootUrlFromRequest(); return null; }And what the corresponding panel code does:f.section(title:_("Jenkins Location")) \{ f.entry(title:_("Jenkins URL"), field:"url") \{ f.textbox(default: Functions.inferHudsonURL(request)) } f.entry(title:_("System Admin e-mail address"), field:"adminAddress") \{ f.textbox() }}So they take the request URI to infer an initial setting. That is why you still see a value when you bring up that panel from our OpenShift Jenkins Image for example.As to changing from the Jenkins console (which is does store the changed version in that file)From "Manage Jenkins" -> "Configure System", you look for the "Jenkins Location" heading and the "Jenkins URL" field Then, the relevant piece of code is [https://github.com/openshift/jenkins-sync-plugin/blob/master/src/main/java/io/fabric8/jenkins/openshiftsync/OpenShiftUtils.java#L448-L462] If the root url from jenkins is set, per that jenkins.model.Jenkins code, we'll get the value from the xml file first. It will use that before trying to discern from the service. You are free to open an RFE (not bug) to make such behavior configurable. thanks
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title
Gabe Montero commented on JENKINS-48079
Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Sorry, I got this bug confused with another one. I refreshed my memory with this and https://bugzilla.redhat.com/show_bug.cgi?id=1510908 Yeah, there was no explicit intention to set the value in the jenkins.model.JenkinsLocationConfiguration.xml file from this plugin We did not want to override an settings the user might have made to that file via Jenkins configuration. or the jenkins service in OpenShift. I'll also not what jenkins.Model.Jenkins.getRootUrl() does: public @Nullable String getRootUrl() { String url = ""> if(url!=null) { return Util.ensureEndsWith(url,"/"); } StaplerRequest req = Stapler.getCurrentRequest(); if(req!=null) return getRootUrlFromRequest(); return null; } And what the corresponding panel code does: f.section(title:_("Jenkins Location")) { f.entry(title:_("Jenkins URL"), field:"url") { f.textbox(default: Functions.inferHudsonURL(request)) } f.entry(title:_("System Admin e-mail address"), field:"adminAddress") { f.textbox() } } So they take the request URI to infer an initial setting. That is why you still see a value when you bring up that panel from our OpenShift Jenkins Image for example. As to changing from the Jenkins console (which is does store the changed version in that file) From "Manage Jenkins" -> "Configure System", you look for the "Jenkins Location" heading and the "Jenkins URL" field Then, the relevant piece of code is https://github.com/openshift/jenkins-sync-plugin/blob/master/src/main/java/io/fabric8/jenkins/openshiftsync/OpenShiftUtils.java#L448-L462 If the root url from jenkins is set, per that jenkins.model.Jenkins code, we'll get the value from the xml file first. It will use that before trying to discern from the service. You are free to open an RFE (not bug) to make such behavior configurable. thanks
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Gabe Montero resolved as Won't Fix Jenkins / JENKINS-48079 jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Change By: Gabe Montero Status: Reopened Resolved Resolution: Won't Fix 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-51223) remoting processing of "no_proxy" env var needs improvement
Title: Message Title Gabe Montero created an issue Jenkins / JENKINS-51223 remoting processing of "no_proxy" env var needs improvement Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-05-09 14:20 Environment: Seen as far back as v3.7 on Jenkins 2.43, and as recent as v3.15 on Jenkins 2.107 Priority: Major Reporter: Gabe Montero The regular _expression_ algorithm in org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.inNoProxyEnvVar(String)(String) does not match when a single element of a fully qualified hostname and domain is part of the no_proxy setting. For example, taking a host name of "jenkins.bnd-cd.svc", we tried adding ".svc", "svc", and "*.svc", "*svc", and none of them matched. We had to specify "bnd-cd.svc" in the no_proxy evn var. By comparison, in th same env, we were able to run curl with a no_proxy evn var containing ".svc" and it properly matched "jenkins.bnd-cd.svc" When running in kubernetes/openshift, having to specify "bnd-cd.svc" is problematic as "bnd-cd" corresponds to the project/namespace, and "svc" was the default suffix applied to all service hostnames. We wanted to have the http_proxy/no_proxy settings be applicable across jenkins running in any project/namespace. In addition to proving this when running an end to end Jenkins master/agent scenario using the standard jar, we also a) took the logic from org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.inNoProxyEnvVar(String) and put it in a simple main program where we set host and no_proxy accordingly b) create debug versions of remoting.jar with additional LOGGER calls to trace the behavior
[JIRA] (JENKINS-51223) remoting processing of "no_proxy" env var needs improvement
Title: Message Title Gabe Montero commented on JENKINS-51223 Re: remoting processing of "no_proxy" env var needs improvement Provided https://github.com/jenkinsci/remoting/pull/269 as a proposal for addressing this. 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero assigned an issue to Gabe Montero Jenkins / JENKINS-53260 exception seen on jenkins 2.138 Change By: Gabe Montero Assignee: Carlos Sanchez Gabe Montero 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero commented on JENKINS-53260 Re: exception seen on jenkins 2.138 Figured out that this was an NPE on the new pod retention code that would escape all the way past https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/slaves/AbstractCloudComputer.java#L63 I'll have a PR up shortly. 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero started work on JENKINS-53260 Change By: Gabe Montero Status: Open In Progress 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero commented on JENKINS-53260 Re: exception seen on jenkins 2.138 PR https://github.com/jenkinsci/kubernetes-plugin/pull/381 submitted 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero commented on JENKINS-53260 Re: exception seen on jenkins 2.138 PR https://github.com/jenkinsci/kubernetes-plugin/pull/381 has merged 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-53260 exception seen on jenkins 2.138 Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed 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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero commented on JENKINS-53260 Re: exception seen on jenkins 2.138 And the resulting commit is in v1.12.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-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero closed an issue as Fixed Verified fix using v1.12.8 Jenkins / JENKINS-53260 exception seen on jenkins 2.138 Change By: Gabe Montero Status: Resolved Closed 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-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Gabe Montero started work on JENKINS-55711 Change By: Gabe Montero Status: Open In Progress 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-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Gabe Montero commented on JENKINS-55711 Re: java.io.FileNotFoundException with tmp file pr https://github.com/openshift/jenkins-client-plugin/pull/214 should address we'll cut v1.0.24 of the plugin when we have finished testing 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-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Gabe Montero commented on JENKINS-55711 Re: java.io.FileNotFoundException with tmp file v1.0.24 of this plugin has been initiated at the update center 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-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-55711 java.io.FileNotFoundException with tmp file Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed 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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title
Gabe Montero commented on JENKINS-36117
Re: OpenShift Deployment Verification Timeout not working
Hi - just wanted to confirm, based on the `retry(3){}` snippet, that you are leveraging the deployment verification logic from a pipeline/workflow plugin groovy script, correct?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working OK, no worries. So two follow ups: 1) with the old Java based step invocation, there was no way to set the waiiTime as part of constructing the step, but with later versions, we now have pipeline DSL, and you can set 'waitTime' as a parameter. See the README and/or try to scriplet generator. 2) If you were using the global jenkins config panel, I do see where the DSL's were not accessing config set there. I'm working on a change to address that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero started work on JENKINS-36117 Change By: Gabe Montero Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working OK I've built a pre-release version of the plugin with the fix noted in 2) of my previous comment. That built plugin can be downloaded from here: https://ci.openshift.redhat.com/jenkins/job/openshift-pipeline-plugin/lastSuccessfulBuild/artifact/plugin/openshift-pipeline.hpi The associated commits are https://github.com/openshift/jenkins-plugin/commit/3b2a329809d7fdf1bbda764dcb5dd0ed602f17e4 https://github.com/jenkinsci/openshift-pipeline-plugin/commit/3b2a329809d7fdf1bbda764dcb5dd0ed602f17e4 Assuming the two follow ups above are in line with what you are doing, if possible, give the new plugin a try and let me know if they resolve this issue for you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero commented on JENKINS-36117 Re: OpenShift Deployment Verification Timeout not working Yep, your assumption is correct, and your welcome I'm going to go ahead and resolve / close this issue. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero closed an issue as Fixed Jenkins / JENKINS-36117 OpenShift Deployment Verification Timeout not working Change By: Gabe Montero Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36117) OpenShift Deployment Verification Timeout not working
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-36117 OpenShift Deployment Verification Timeout not working Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [openshift-pipeline-plugin] (JENKINS-31483) openshift plugin appears to be compiled for JDK8 only
Title: Message Title Gabe Montero commented on JENKINS-31483 Re: openshift plugin appears to be compiled for JDK8 only Turns out, a dependency of the plugin requires 1.8. I'm in the process of seeing how difficult it is to remove that restriction. I hope to resolve one way or the other in the next couple of days. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [openshift-pipeline-plugin] (JENKINS-31483) openshift plugin appears to be compiled for JDK8 only
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-31483 openshift plugin appears to be compiled for JDK8 only Change By: Gabe Montero Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [openshift-pipeline-plugin] (JENKINS-31483) openshift plugin appears to be compiled for JDK8 only
Title: Message Title Gabe Montero commented on JENKINS-31483 Re: openshift plugin appears to be compiled for JDK8 only The 1.8 dependency is going to remain. I've updated the WIKI and readme's. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-59940) Openshift sync plugin 1.0.42 stop working due to problem with credentials
Title: Message Title Gabe Montero assigned an issue to Akram Ben Aissi Jenkins / JENKINS-59940 Openshift sync plugin 1.0.42 stop working due to problem with credentials Change By: Gabe Montero Assignee: Gabe Montero Akram Ben Aissi 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.202742.1572022935000.1890.1572023220187%40Atlassian.JIRA.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero commented on JENKINS-58382 Re: Build is stuck due to blocked thread hey Ariel M - without seeing the full thread dump, it is hard to say. Possibly cancelling all openshift pipeline strategy builds running on jenkins might help. Otherwise, restarting Jenkins is the only option. I think I have enough from the single thread stack trace to devise a fix, but again, if by some chance you have the full thread dump still, please attach as a text file (posting them as Jira comments are hard to read). thanks 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.200506.1562597218000.4963.1562607720159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero started work on JENKINS-58382 Change By: Gabe Montero Status: Open In Progress 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.200506.1562597218000.10097.1563131100222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero commented on JENKINS-58382 Re: Build is stuck due to blocked thread PR https://github.com/openshift/jenkins-sync-plugin/pull/317 is up for addressing the deadlock After it merges, I'll cherry pick it into https://github.com/jenkinsci/openshift-sync-plugin and cut a new version of the 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.200506.1562597218000.10099.1563131160149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero commented on JENKINS-58382 Re: Build is stuck due to blocked thread I think so yes 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.200506.1562597218000.11802.1563266640095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero commented on JENKINS-58382 Re: Build is stuck due to blocked thread so v1.0.39 of the sync plugin has been released and it has the fix thanks 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.200506.1562597218000.14065.1563370380109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-58382 Build is stuck due to blocked thread Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed Released As: v1.0.39 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.200506.1562597218000.14067.1563370440362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58382) Build is stuck due to blocked thread
Title: Message Title Gabe Montero commented on JENKINS-58382 Re: Build is stuck due to blocked thread because the parameter propagation goes through some of the same callback channels that your original deadlock went through Ariel That said, without debug data, I'm making an educated guess. But if you want to pursue debugging, open a separate issue and provide another thread dump and the jenkins logs / job logs when the failure occurs. 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.200506.1562597218000.14542.1563377524720%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Gabe Montero assigned an issue to Vibhav Bobade Jenkins / JENKINS-58179 Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Change By: Gabe Montero Assignee: Vibhav Bobade 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.200230.1561449713000.15255.1563450240302%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Gabe Montero commented on JENKINS-58179 Re: Jenkins builds disappearing from Unix machine due to open shift sync plugin issue A couple of points Ariel: a) actually I've just transferred ownership of the openshift/jenkins stuff to another team within RedHat. I've assigned one of those developers here. b) that said, you've encountered a known feature with our sync plugin, where the sync plugin will delete associated runs for build the openshift build controller deletes on the openshift side You can control pruning on the openshift side via https://docs.openshift.com/container-platform/3.11/dev_guide/builds/advanced_build_operations.html#build-pruning there are no separate controls on the sync plugin side to turn on and off but you can work with Vibhav about requesting a new feature if the openshift side controls are not sufficient 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.200230.1561449713000.15260.1563450540133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
