[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Vincent Rivellino commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Ximon - not sure if you noticed, but your pull request (#131) has merge conflicts now. I'd love to see this issue resolved! 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] [depgraph-view-plugin] (JENKINS-27996) dependency graph viewer plugin gives gets NaN in jsplumb mode
Maxim Nikolaev commented on JENKINS-27996 dependency graph viewer plugin gives gets NaN in jsplumb mode More error info from chrome: Error: Invalid value for svg attribute width="NaN" Error: Invalid value for svg attribute height="NaN" Error: Invalid value for path attribute d="M NaN NaN C NaN NaN NaN NaN NaN NaN" Error: Invalid value for path attribute d="MNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN" 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] [core] (JENKINS-28002) Error 503 when cancelling job
Sylvain ANGLADE created JENKINS-28002 Error 503 when cancelling job Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Apr/15 12:50 PM Description: When canceling a work in progress on jenkins which lasted more than two hours, the server stops and there is a 503 error. I enclose jenkins logs in this error. I work on a Ubunut 14.04 LTS with Apache reverse proxy. Log : INFO: rr_tomato #3 aborted java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at java.lang.UNIXProcess.waitFor(UNIXProcess.java:263) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Environment: Ubuntu 14.04 LTS, Opend JDK 7, plugins : Build Setter Name, Greenball, ANSI Color, Schedule Build Project: Jenkins Labels: jenkins Priority: Minor Reporter: Sylvain ANGLADE 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] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Andreas W commented on JENKINS-17431 500 Internal Server Error on attempt to run a build We are using Jenkins 1.596.2 with subversion plugin 2.5 and can then observe exact the same problem. With subversion plugin 2.4.5 everything is okay. Switched back to 2.5, same problem again. However with subversion plugin 2.4.5 we cannot use the the subversion plugin as of 2.5. So this is a real blocker for us. As this is not the first problem with the subversion plugin, I am currently trying to replace the subversion plugins by scripts which call the command-line subversion tool. 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] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Andreas W commented on JENKINS-17431 500 Internal Server Error on attempt to run a build For reference, here is our stack trace, maybe the slight differences are a result of calling it from workflow plugin, but the error occurs in every job, regardless which type: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS of 'xx': 500 Internal Server Error () svn: E175002: OPTIONS request failed on 'xx' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:106) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:90) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:764) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:175) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:480) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getLocations(SVNBasicDelegate.java:833) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:527) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:875) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:66) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:18) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) at hudson.FilePath.act(FilePath.java:981) at hudson.FilePath.act(FilePath.java:959) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:106) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:100) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:69) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Dominic Bishop commented on JENKINS-25203 support embedded content in json I've just completed some initial quick tests with the snapshot. When running the build on Jenkins master it completed without error and successfully parsed the screenshot that was embedded in the JSON. I was able to view this ok by following the embedded link from the test scenario result page. It would be nice if this could be inlined there however if possible to avoid the extra click to see the image. I am using this to capture a browser screenshot on failure of a UI scenario so being able to see it in context of the assertion message would be much easier to work with than having them on 2 different URLs. When I tested with the job running on a slave however the publish of results failed, here is the stacktrace I received: 21:09:47 Cucumber Tests Parsing results. 21:09:47 Cucumber Tests parsing report.json 21:09:48 ERROR: Failed to archive cucumber reports 21:09:48 java.io.IOException: remote file operation failed: /tank/jenkins/workspace/Cucumber_Plugin_Test at hudson.remoting.Channel@4538bceb:jenkins-minion-001.vagrant.com: java.io.IOException: Unable to serialize org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResult@58776ea5 21:09:48 at hudson.FilePath.act(FilePath.java:985) 21:09:48 at hudson.FilePath.act(FilePath.java:967) 21:09:48 at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl.parse(DefaultTestResultParserImpl.java:100) 21:09:48 at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:114) 21:09:48 at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.perform(CucumberTestResultArchiver.java:95) 21:09:48 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 21:09:48 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) 21:09:48 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) 21:09:48 at hudson.model.Build$BuildExecution.post2(Build.java:183) 21:09:48 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) 21:09:48 at hudson.model.Run.execute(Run.java:1766) 21:09:48 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 21:09:48 at hudson.model.ResourceController.execute(ResourceController.java:98) 21:09:48 at hudson.model.Executor.run(Executor.java:374) 21:09:48 Caused by: java.io.IOException: Unable to serialize org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResult@58776ea5 21:09:48 at hudson.remoting.UserRequest.serialize(UserRequest.java:169) 21:09:48 at hudson.remoting.UserRequest.perform(UserRequest.java:129) 21:09:48 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 21:09:48 at hudson.remoting.Request$2.run(Request.java:324) 21:09:48 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 21:09:48 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 21:09:48 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 21:09:48 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 21:09:48 at hudson.remoting.Engine$1$1.run(Engine.java:63) 21:09:48 at java.lang.Thread.run(Thread.java:745) 21:09:48 at ..remote call to jenkins-minion-001.vagrant.com(Native Method) 21:09:48 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) 21:09:48 at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) 21:09:48 at hudson.remoting.Channel.call(Channel.java:753) 21:09:48 at hudson.FilePath.act(FilePath.java:978) 21:09:48 ... 13 more 21:09:48 Caused by: java.io.NotSerializableException: org.jenkinsci.plugins.cucumber.jsontestsupport.EmbeddedItem 21:09:48 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183) 21:09:48 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) 21:09:48 at java.util.ArrayList.writeObject(ArrayList.java:742) 21:09:48 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) 21:09:48 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 21:09:48 at java.lang.reflect.Method.invoke(Method.java:606) 21:09:48 at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) 21:09:48 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1495) 21:09:48 at
Hello
I have something important to share with you, but I want your consent before sending details for full explanation -- 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] [ec2-plugin] (JENKINS-28003) ec2-plugin breaks with BouncyCastle 1.50
Nathan Grennan created JENKINS-28003 ec2-plugin breaks with BouncyCastle 1.50 Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 18/Apr/15 7:53 PM Description: The issue is it errors on use of the "Test Connection" button in "Configure System". It tries to load "org/bouncycastle/asn1/DERObject" for the "EC2 Key Pair's Private Key". Fedora includes BouncyCastle 1.50, which drops the org.bouncycastle.openssl classes required by ec2-plugin 1.27. ec2-plugins includes the older version of BouncyCastle, 1.40, but the system version overrides it. So I set maven to include plugin libraries and classes in the Classpath version during compile. Along with explicitly masking org.bouncycastle. I created a pull request on the ec2-plugin github repo, PR #145. An alternative fix would be to rewrite the ec2-plugin to use the newer version of BouncyCastle, or rewrite that part to use a library other than BouncyCastle. Environment: ec2-plugin 1.27 Jenkins 1.609(custom package built from the Fedora 22 1.606 package) Fedora 21 x86_64 Project: Jenkins Priority: Major Reporter: Nathan Grennan 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] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Dominic Bishop commented on JENKINS-25203 support embedded content in json A further follow up to this. I'm seeing some very weird behaviour with the URL to access the embedded item. I got a 404 at one point and I have done a little bit more experimentation. If I have a URL to an embedded item open, e.g. http://192.168.0.2:8080/job/Cucumber_Plugin_Test/lastCompletedBuild/cucumberTestReport/checkout-flows/anonymous-checkout-flow/embed/cuke_2848226563976186823.embed and repeatedly refresh the page then it alternates between showing me the image and giving me a 404: HTTP ERROR 404 Problem accessing /job/Cucumber_Plugin_Test/lastCompletedBuild/cucumberTestReport/checkout-flows/anonymous-checkout-flow/embed/cuke_2848226563976186823.embed. Reason: Not Found This isn't random, it is a cycle between found-not found-found-not found etc. In the Jenkins log I see this appear everytime the 404 is served: Apr 18, 2015 9:33:31 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn Committed before 404 null 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] [warnings-plugin] (JENKINS-27377) Custom view does not display job warnings, displays '0'
Evan Benn commented on JENKINS-27377 Custom view does not display job warnings, displays 0 By custom view I just meant the normal filtered list of jobs you can create. The warnings are shown correctly in the job, they are being counted correctly by the parser. The only part with an issue is that the column in the view of jobs does not display the same number as is displayed on the job page. I will try to get a screenshot on Monday. 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] [core] (JENKINS-27991) Unable to POST modified config.xml in Jenkins via curl API.
Daniel Beck commented on JENKINS-27991 Unable to POST modified config.xml in Jenkins via curl API. To clarify, it works on 1.596, but does not work on 1.596.1? Do I need to consider any dependent plugin as per the version compatible? I don't understand the question. 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Daniel Beck resolved JENKINS-27972 as Duplicate Credentials Scope dropdown is empty for new entry Change By: Daniel Beck (18/Apr/15 7:43 AM) Status: Reopened Resolved Resolution: Duplicate 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] [checkstyle-plugin] (JENKINS-27887) pmd plugin and checkstyle plugin fail to install
Daniel Beck commented on JENKINS-27887 pmd plugin and checkstyle plugin fail to install Also, disable the Windows search indexer service. 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Daniel Beck reopened JENKINS-27972 Credentials Scope dropdown is empty for new entry Change By: Daniel Beck (18/Apr/15 7:42 AM) Resolution: Fixed Status: Resolved Reopened Assignee: stephenconnolly 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] [core] (JENKINS-27967) Remote trigger from Fisheye webhook
Daniel Beck commented on JENKINS-27967 Remote trigger from Fisheye webhook It looks to me like you're asking for better support/integration of a specific other tool/program, and that doesn't really belong in core. Hence my question. What URL in Jenkins do you configure in the hook? 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] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Daniel Beck updated JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 Looks like a bug in Priority Sorter plugin. Change By: Daniel Beck (18/Apr/15 7:47 AM) Assignee: MagnusSandberg Component/s: prioritysorter-plugin Component/s: core 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Daniel Beck commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 Possibly related to the queue concurrency issue introduced in 1.536 or so. Apparently it's easiest to see when you only have one CPU core, no hyperthreading. That was resolved in 1.607, with further fixes in 1.610 (no changelog entry for that yet). 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] [other] (JENKINS-28001) [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL glo
Dimitri Tenenbaum assigned JENKINS-28001 to Dimitri Tenenbaum [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings) Change By: Dimitri Tenenbaum (18/Apr/15 7:10 AM) Assignee: DimitriTenenbaum 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.
