[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name
Title: Message Title Michael Merritt edited a comment on JENKINS-34512 Re: error in build-name-setter plugin - Set build name Thanks for the tip on reverting, that also fixed it for us after upgrading to BNSP 1 . 6.5 (from 1.5.1) 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] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name
Title: Message Title Michael Merritt commented on JENKINS-34512 Re: error in build-name-setter plugin - Set build name Thanks for the tip on reverting, that also fixed it for us. 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] [sauce-ondemand-plugin] (JENKINS-31376) Sauce connect intermmentantly fails to launch
Title: Message Title Michael Merritt commented on JENKINS-31376 Re: Sauce connect intermmentantly fails to launch Also, we do have other failures with the plug-in sometimes not coming up. How do we provide the most info for debugging these issues? Thanks. 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] [sauce-ondemand-plugin] (JENKINS-31376) Sauce connect intermmentantly fails to launch
Title: Message Title Michael Merritt closed an issue as Fixed Closing, this appeared to be related to one of Sauce's outages. Jenkins / JENKINS-31376 Sauce connect intermmentantly fails to launch Change By: Michael Merritt Status: Open Closed 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] [sauce-ondemand-plugin] (JENKINS-31376) Sauce connect intermmentantly fails to launch
Title: Message Title Michael Merritt updated an issue Jenkins / JENKINS-31376 Sauce connect intermmentantly fails to launch Change By: Michael Merritt Since upgrading Jenkins and sauce connect -ondemand we are having mostly failures with sauce connect launching. Occasionally sauce does launch correctly. Jenkins is running on Ubuntu 12.04, but we're launching sauce on the slave which is Debian 6.0.10. We are not using sauce on demand 1.142 because that was working even worse for us. Starting Sauce Connect on slave node using tunnel identifier: test-pull-requests-jsunit-tests-1446583886414Launching Sauce Connect on localhost03 Nov 20:51:04 - Sauce Connect 4.3.11, build 1757 2b421bb03 Nov 20:51:04 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt.03 Nov 20:51:04 - Using CA certificate verify path /etc/ssl/certs.03 Nov 20:51:04 - Starting up; pid 778903 Nov 20:51:04 - Command line arguments: /home/autotest/sc-4.3.11-linux/bin/sc -u jenkinsbuild -k -P 444503 Nov 20:51:04 - Using no proxy for connecting to Sauce Labs REST API.03 Nov 20:51:04 - Resolving saucelabs.com to 162.222.75.243 took 1 ms.03 Nov 20:51:04 - Started scproxy on port 35287.03 Nov 20:51:04 - Please wait for 'you may start your tests' to start your tests.03 Nov 20:51:04 - Starting secure remote tunnel VM...03 Nov 20:51:09 - Secure remote tunnel VM provisioned.03 Nov 20:51:09 - Tunnel ID: 98cdb43fe69b49c48ef2098d332ceded03 Nov 20:51:09 - Secure remote tunnel VM is now: booting03 Nov 20:52:16 - Error bringing up tunnel VM.03 Nov 20:52:16 - Sauce Connect could not establish a connection.03 Nov 20:52:16 - Please check your firewall and proxy settings.03 Nov 20:52:16 - You can also use sc --doctor to launch Sauce Connect in diagnostic mode.03 Nov 20:52:16 - Cleaning up.03 Nov 20:52:16 - Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy03 Nov 20:52:16 - Overlapping domain: sauce-connect.proxy, shutting down tunnel 98cdb43fe69b49c48ef2098d332ceded.03 Nov 20:52:19 - Goodbye.Error launching Sauce ConnectFlushing Sauce Connect Input StreamFlushing Sauce Connect Error StreamClosing Sauce Connect processFATAL: Error launching Sauce Connectcom.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:320) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:841) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:777) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to pullrequests.www.dash.d1.usw1.opendns.com(Native Method) at
[JIRA] [sauce-ondemand-plugin] (JENKINS-31376) Sauce connect intermmentantly fails to launch
Title: Message Title Michael Merritt created an issue Jenkins / JENKINS-31376 Sauce connect intermmentantly fails to launch Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 03/Nov/15 9:08 PM Environment: Jenkins 1.635, Debian GNU/Linux 6.0.10, Sauce OnDemand plugin 1.140 Priority: Major Reporter: Michael Merritt Since upgrading Jenkins and sauce connect we are having mostly failures with sauce connect launching. Occasionally sauce does launch correctly. Jenkins is running on Ubuntu 12.04, but we're launching sauce on the slave which is Debian 6.0.10. Starting Sauce Connect on slave node using tunnel identifier: test-pull-requests-jsunit-tests-1446583886414 Launching Sauce Connect on localhost 03 Nov 20:51:04 - Sauce Connect 4.3.11, build 1757 2b421bb 03 Nov 20:51:04 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt. 03 Nov 20:51:04 - Using CA certificate verify path /etc/ssl/certs. 03 Nov 20:51:04 - Starting up; pid 7789 03 Nov 20:51:04 - Command line arguments: /home/autotest/sc-4.3.11-linux/bin/sc -u jenkinsbuild -k -P 4445 03 Nov 20:51:04 - Using no proxy for connecting to Sauce Labs REST API. 03 Nov 20:51:04 - Resolving saucelabs.com to 162.222.75.243 took 1 ms. 03 Nov 20:51:04 - Started scproxy on port 35287. 03 Nov 20:51:04 - Please wait for 'you may start your tests' to
[JIRA] [sauce-ondemand-plugin] (JENKINS-31376) Sauce connect intermmentantly fails to launch
Title: Message Title Michael Merritt commented on JENKINS-31376 Re: Sauce connect intermmentantly fails to launch This might be related to sauce labs outage. Waiting to see. 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] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Michael Merritt commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Thanks, we'll give it a try. 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] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title
Michael Merritt edited a comment on JENKINS-27371
Re: Parent builds sometimes hang on successful child builds of same type
We'realsoseeingthissameissuethatSimonisdescribingandit'scausingdeployheadachesforus.Frequentlyhavingtokillthejobandrebuilditandrollthedicetoseeifit'sgoingtowork.Ourlogslooksimilartothosementionedabove.Jenkins1.607Multijob1.16 {code:java} website-deploy-production-download#10432mainbuildactioncompleted:SUCCESSJun10,20158:50:19PMSEVEREhudson.model.Executorfinish1Executorthrewanexceptionjava.util.NoSuchElementException atjenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) atjenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) atjava.util.AbstractMap$2$1.next(AbstractMap.java:385) athudson.util.RunList.subList(RunList.java:137) athudson.tasks.LogRotator.perform(LogRotator.java:124) athudson.model.Job.logRotate(Job.java:465) athudson.model.Run.execute(Run.java:1805) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:374) {code}
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] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Michael Merritt commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type We're also seeing this same issue that Simon is describing and it's causing deploy headaches for us. Frequently having to kill the job and rebuild it and roll the dice to see if it's going to work. Our logs look similar to those mentioned above. Jenkins 1.607 Multijob 1.16 website-deploy-production-download #10432 main build action completed: SUCCESS Jun 10, 2015 8:50:19 PM SEVERE hudson.model.Executor finish1 Executor threw an exception java.util.NoSuchElementException at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.subList(RunList.java:137) at hudson.tasks.LogRotator.perform(LogRotator.java:124) at hudson.model.Job.logRotate(Job.java:465) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) 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] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title
Michael Merritt edited a comment on JENKINS-27371
Re: Parent builds sometimes hang on successful child builds of same type
We'realsoseeingthissameissuethatSimonisdescribingandit'scausingdeployheadachesforus.Frequentlyhavingtokillthejobandrebuilditandrollthedicetoseeifit'sgoingtowork.Ourlogslooksimilartothosementionedabove. Letmeknowifyouneedmoreinfo. Jenkins1.607Multijob1.16{code:java}website-deploy-production-download#10432mainbuildactioncompleted:SUCCESSJun10,20158:50:19PMSEVEREhudson.model.Executorfinish1Executorthrewanexceptionjava.util.NoSuchElementException atjenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) atjenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) atjava.util.AbstractMap$2$1.next(AbstractMap.java:385) athudson.util.RunList.subList(RunList.java:137) athudson.tasks.LogRotator.perform(LogRotator.java:124) athudson.model.Job.logRotate(Job.java:465) athudson.model.Run.execute(Run.java:1805) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:374){code}
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] [ghprb-plugin] (JENKINS-26415) Default success/failure message of GHPRB can't be saved
Michael Merritt commented on JENKINS-26415 Default success/failure message of GHPRB cant be saved Yes please fix. As a perfectionist this drives me crazy seeing case difference in every email sent out to our team and I hate that I can't save a custom message. I was able to save one for about a day before it reverted on it's own, oddly enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sauce-ondemand-plugin] (JENKINS-27111) Sauce Connect intermittently fails to launch
Michael Merritt resolved JENKINS-27111 as Fixed Sauce Connect intermittently fails to launch This appears to be resolved with Sauce Connect 4.3.8 Will continue to test and re-open if we see it again. Thanks for your help Ross. Change By: Michael Merritt (07/Apr/15 11:13 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sauce-ondemand-plugin] (JENKINS-27111) Sauce Connect intermittently fails to launch
Michael Merritt commented on JENKINS-27111 Sauce Connect intermittently fails to launch @Ross - Logged a sauce labs support ticket with requested information on behalf of nick. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Michael Merritt edited a comment on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild Also seeing this same error fairly frequently in jenkins 1.605 and multijob plugin 1.16. Haven't seen it disrupt the our multi-jobs yet, but seeing it frequently in the logs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Michael Merritt commented on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild Also seeing this same error fairly frequently in jenkins 1.605 and multijob plugin 1.16 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Michael Merritt edited a comment on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild Nevermind, re-reporting an old issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Michael Merritt edited a comment on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild We're also experiencing this same issue, but environment ubuntu 14.04. Are people just not using this plug-in? Thanks. (wasn't sure to log a separate bug for ubuntu). Jenkins v1.589 Multi-job 1.15 Update: Reverting to 1.13 resolved the warning for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Michael Merritt commented on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild We're also experiencing this same issue, but environment ubuntu 14.04. Is there any work-around? Does a lower version help? Or are people just not using this plug-in? Thanks. (wasn't sure to log a separate bug for ubuntu). Jenkins v1.589 Multi-job 1.15 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
