[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report James Dumay it touches several aspects of BO. See key findings above. For example UI should stop sending redundant calls costing multiple of seconds, cache JS scripts across pages, investigate why SSE configure for job subscription is expensive, Favourite and search API performance etc. you should split it in to multiple tickets and assign right people to it. For favorite Ivan or me should look in to. I plan to take on search for sure. 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-37958) Editor feedback
Title: Message Title Josh McDonald closed an issue as Fixed These should be sorted now, with the exception of the step reordering. Going to focus on JENKINS-38051 Jenkins / JENKINS-37958 Editor feedback Change By: Josh McDonald Status: Open Closed 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
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Matthew Reiter commented on JENKINS-31487 Re: Job status not updated in web UI during build I've created the pull request: https://github.com/jenkinsci/jenkins/pull/2542 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-37337) Pipeline scripts that appear as "queued" in classic UI are not returned from /queue API
Title: Message Title James Dumay commented on JENKINS-37337 Re: Pipeline scripts that appear as "queued" in classic UI are not returned from /queue API ack 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-38079) Investigate performance degradation report
Title: Message Title James Dumay commented on JENKINS-38079 Re: Investigate performance degradation report Thanks Vivek Pandey - where are you going to start? 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title James Dumay commented on JENKINS-35864 Re: Step section in log sticks to result header when scrolling Michael Neale probably want Brody to help with the interaction on this one. 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-38067) Failure to call Util.encode
Title: Message Title James Dumay updated JENKINS-38067 Jenkins / JENKINS-38067 Failure to call Util.encode Change By: James Dumay Status: In Review 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] (JENKINS-38082) ContainerFilter should use Iterables.filter internally
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-38082 ContainerFilter should use Iterables.filter internally Change By: James Dumay Assignee: Ivan Meredith 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-38117) After disabling the plugin "Test result Trend" still displayed
Title: Message Title Constantin Bugneac created an issue Jenkins / JENKINS-38117 After disabling the plugin "Test result Trend" still displayed Issue Type: Bug Assignee: Varun Menon Attachments: Capture.JPG Components: test-results-analyzer-plugin Created: 2016/Sep/10 6:43 PM Environment: Jenkins 2.21 CentOS 7.2 openjdk version "1.8.0_101" Labels: jenkins test-results Priority: Minor Reporter: Constantin Bugneac Hi, After the plugin is disabled, un-installed and Jenkins restarted the project job still displays the test results artifacts. See attachment. It doesn't properly clean up after un-install. Regards, Constantin
[JIRA] (JENKINS-37449) EC2-plugin preventing Jenkins from starting if a slave is dead
Title: Message Title Brent Courtois commented on JENKINS-37449 Re: EC2-plugin preventing Jenkins from starting if a slave is dead Jeff Gaston Thank you for the info. I took a different route that doesn't fix the problem but it prevents jenkins from failing to start up, I'll leave it here in case anyone needs to circumvent the same issue: 1. Go to jenkins home directory and manually delete the ec2 plugins jpi file. 2. In the jenkin's home's nodes directory removed the directory of the agent that wasn't up anymore. 3. Restarted jenkins and reinstalled the ec2 plugin. 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-31615) Sometimes the plugin leaves behind a stale PID file or zombie Sauce Connect process, should the plugin handle this?
Title: Message Title Gavin Mogan commented on JENKINS-31615 Re: Sometimes the plugin leaves behind a stale PID file or zombie Sauce Connect process, should the plugin handle this? okay cool, we'll look into it. i suspect once you finish upgrading to the jenkins plugin this will be delt with. 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-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title magnayn updated an issue Jenkins / JENKINS-35184 Failed to load jenkins.util.SystemProperties on slaves due to ServletContext Change By: magnayn Priority: Critical Blocker 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-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title magnayn commented on JENKINS-35184 Re: Failed to load jenkins.util.SystemProperties on slaves due to ServletContext I have this error too (Jenkins 2.7) Slave is evargas/jenkins-slave docker image (1.7.0_101), master is 1.8. [09/10/16 16:52:18] [SSH] Starting slave process: cd "/home/jenkins" && java -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.59 This is a Unix agent java.io.IOException: Remote call on docker-cb0efbf57eef failed at hudson.remoting.Channel.call(Channel.java:789) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:536) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:381) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:901) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:126) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:658) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) 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) Caused by: java.lang.LinkageError: Failed to load jenkins.util.SystemProperties at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:342) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:251) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at hudson.util.RingBufferLogHandler.(RingBufferLogHandler.java:39) at hudson.slaves.SlaveComputer$LogHolder.(SlaveComputer.java:799) at hudson.slaves.SlaveComputer$SlaveInitializer.call(SlaveComputer.java:808) at hudson.slaves.SlaveComputer$SlaveInitializer.call(SlaveComputer.java:802) at hudson.remoting.UserRequest.perform(UserRequest.java:152) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to docker-cb0efbf57eef(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:252) at hudson.remoting.Channel.call(Channel.java:781) ... 10 more Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletContextListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:803) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:338) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:251) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at hudson.util.RingBufferLogHandler.(RingBufferLogHandler.java:39) at hudson.slaves.SlaveComputer$LogHolder.(SlaveComputer.java:799) at hudson.slaves.SlaveComputer$SlaveInitializer.call(SlaveComputer.java:808) at hudson.slaves.SlaveComputer$SlaveInitializer.call(SlaveComputer.java:802) at hudson.remoting.UserRequest.perform(UserRequest.java:152) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at
[JIRA] (JENKINS-38008) unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is
Title: Message Title krishna b assigned an issue to Michael Fazio Jenkins / JENKINS-38008 unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is able to open Change By: krishna b Assignee: krishna b Michael Fazio 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-38008) unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is
Title: Message Title Michael Fazio assigned an issue to krishna b Jenkins / JENKINS-38008 unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is able to open Change By: Michael Fazio Assignee: Michael Fazio krishna b 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-38008) unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is
Title: Message Title Michael Fazio commented on JENKINS-38008 Re: unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is able to open I think that this issue has been raised against the wrong plugin. This hp-quality-center-plugin collects unit tests results from a maven build and uploads them to an HP ALM quality center instance using the RESTful web api. It has no knowledge of UFT etc. 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-38116) Add duration time to flow graph table in pipeline steps
Title: Message Title JT Chu created an issue Jenkins / JENKINS-38116 Add duration time to flow graph table in pipeline steps Issue Type: New Feature Assignee: Jesse Glick Components: pipeline Created: 2016/Sep/10 12:39 PM Labels: pipeline Priority: Major Reporter: JT Chu Currently in the pipeline steps (flow graph table), there is only status icon display. I would like to request to add duration time to this view. This can help to figure out the speed up or slow down of each steps. Add Comment
[JIRA] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title Katherine Morgan edited a comment on JENKINS-33846 Re: Restart pipeline from specific stage, after failure I really really really want this feature. And it is absolutely going to stop me from using the pipeline functionality. I just spent a full day implementing my build and deployment process with the pipeline functionality. I have builds that progress through these stages: BUILD > DEV > STAGE > INTEG > PREPROD > PROD. I'm using the 'waiting for input' feature to capture human approval to progress the deployment to the next environment. In testing it, I found that the pipelines would fill my 'build executor status' list whilst they were 'waiting for approval', and would block jenkins from doing any more work. Just not usable. If the 'restart a stage' feature existed, I could then deploy any pipeline to any environment, achieving build progression and rollback.*UPDATE:* I've since learnt that I need to move my input to outside of a node, this resolves my blocked executors. 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-35503) Slack plugin reveals integration token
Title: Message Title Kurt Madel commented on JENKINS-35503 Re: Slack plugin reveals integration token See https://github.com/jenkinsci/slack-plugin/pull/247 for initial fix. Still allows users to expose auth token but provides highly visible warning. 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-34222) Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job
Title: Message Title Sultan Maiyaki commented on JENKINS-34222 Re: Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job Hi.. I might be late to this discussion but this issue can be resolved by installing the ZAPI plugin in JIRA. The plugin allows for programmatic access to test data via REST APIs. This needs to be in JIRA for jenkins to be able to post the test results 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-33253) Unable to use multiple AWS credentials across jobs
Title: Message Title Mohamed Pakkeer commented on JENKINS-33253 Re: Unable to use multiple AWS credentials across jobs We are facing the same issue on our production Jenkins server. We have a separate AWS account for staging and production. We initially configured staging AWS credential for staging job. It is working fine for staging job. We faced issue when we try to add the production aws credential for production job. When we click the credential plugin tab,it shows the staging account credential two times .We can't select/use the production aws credential for production job. Any help will be greatly appreciated. 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-33253) Unable to use multiple AWS credentials across jobs
Title: Message Title Mohamed Pakkeer updated an issue Jenkins / JENKINS-33253 Unable to use multiple AWS credentials across jobs Change By: Mohamed Pakkeer Attachment: screenshot-1.png 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-37515) pipeline input blocks the executor
Title: Message Title Katherine Morgan commented on JENKINS-37515 Re: pipeline input blocks the executor Thanks for the tip Jesse Glick, that resolved it for me. 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-38098) "Error reading timestamps for ..."
Title: Message Title Makson Lee commented on JENKINS-38098 Re: "Error reading timestamps for ..." we have the same issue. jenkins: 2.21 timestamper: 1.8.5 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-33846) Restart pipeline from specific stage, after failure
Title: Message Title Jean-Marc Collin commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure Ideally this plugin should be organized as it is done in DeliveryPlugin: you can group steps into stage, display each steps and stage and add a restart button on each steps and stage. Please take a look at the delivery Pipeline link here. I wonder if merging the both pulgin to take the best of each is not the best solution. 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-33846) Restart pipeline from specific stage, after failure
Title: Message Title Katherine Morgan commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure I really really really want this feature. And it is absolutely going to stop me from using the pipeline functionality. I just spent a full day implementing my build and deployment process with the pipeline functionality. I have builds that progress through these stages: BUILD > DEV > STAGE > INTEG > PREPROD > PROD. I'm using the 'waiting for input' feature to capture human approval to progress the deployment to the next environment. In testing it, I found that the pipelines would fill my 'build executor status' list whilst they were 'waiting for approval', and would block jenkins from doing any more work. Just not usable. If the 'restart a stage' feature existed, I could then deploy any pipeline to any environment, achieving build progression and rollback. 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.
