[JIRA] [credentials-plugin] (JENKINS-35149) The credentials plugin configuration should show the timestamp and the job which last used the current credentials object
Title: Message Title Cristian Magherusan-Stanciu updated an issue Jenkins / JENKINS-35149 The credentials plugin configuration should show the timestamp and the job which last used the current credentials object Change By: Cristian Magherusan-Stanciu This should be shown in the UI as another pair of fields in the heading shown in the view below.!current-UI.png! 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] [credentials-plugin] (JENKINS-35149) The credentials plugin configuration should show the timestamp and the job which last used the current credentials object
Title: Message Title Cristian Magherusan-Stanciu updated an issue Jenkins / JENKINS-35149 The credentials plugin configuration should show the timestamp and the job which last used the current credentials object Change By: Cristian Magherusan-Stanciu Attachment: current-UI.png 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] [credentials-plugin] (JENKINS-35149) The credentials plugin configuration should show the timestamp and the job which last used the current credentials object
Title: Message Title Cristian Magherusan-Stanciu created an issue Jenkins / JENKINS-35149 The credentials plugin configuration should show the timestamp and the job which last used the current credentials object Issue Type: New Feature Assignee: stephenconnolly Components: credentials-plugin Created: 2016/May/26 12:20 PM Priority: Minor Reporter: Cristian Magherusan-Stanciu Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [changelog-history-plugin] (JENKINS-31934) Split changelog by repository when using the multiple SCM plugin
Title: Message Title Cristian Magherusan-Stanciu created an issue Jenkins / JENKINS-31934 Split changelog by repository when using the multiple SCM plugin Issue Type: Improvement Assignee: Kevin Bell Components: changelog-history-plugin, multiple-scms-plugin Created: 07/Dec/15 11:06 AM Priority: Minor Reporter: Cristian Magherusan-Stanciu In my company we use the SCM plugin a lot for aggregating various components located in different repos, and we would find our changelogs much more useful if they would be split by repository in which the changes happened. At the moment they are split by the type of SCM (git, SVN ,etc.) but that's not useful if you have only multiple git repos and no SVN repo, for example. We just see a list of all the changes that happened across all those git repos which is not really useful. Add Comment
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marjed as failed
Cristian Magherusan-Stanciu created JENKINS-27415 Junit plugin fails to parse output, all tests are marjed as failed Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 13/Mar/15 1:30 PM Description: Jobs fail all tests and are always unstable, and this error shows up when parsing the results: Failed to read test report file /var/lib/jenkins/workspace/MH5_Pipeline_02_Unit_tests/reports/client/unit/TEST-Firefox_360_Linux.nokia.mh5.adapters.IpLookup.xml org.dom4j.DocumentException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAX Messages Nested exception: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMe ssages at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123) at hudson.tasks.junit.TestResult.parse(TestResult.java:282) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:228) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:146) at hudson.tasks.junit.TestResult.init(TestResult.java:122) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:119) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:93) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) 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) Caused by: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174) at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166) at java.security.AccessController.doPrivileged(Native Method) at com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166) at com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:57) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.getProperty(AbstractSAXParser.java:2062) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty(SAXParserImpl.java:579) at org.dom4j.io.SAXHelper.setParserProperty(SAXHelper.java:34) at org.dom4j.io.SAXReader.configureReader(SAXReader.java:911) at org.dom4j.io.SAXReader.read(SAXReader.java:463) ... 18 more Nested exception: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174) at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166) at java.security.AccessController.doPrivileged(Native Method) at com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166) at com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:57) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.getProperty(AbstractSAXParser.java:2062) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty(SAXParserImpl.java:579) at
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marked as failed
Cristian Magherusan-Stanciu updated JENKINS-27415 Junit plugin fails to parse output, all tests are marked as failed Change By: Cristian Magherusan-Stanciu (13/Mar/15 1:52 PM) Summary: Junitpluginfailstoparseoutput,alltestsare marjed marked asfailed 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] [pollscm-plugin] (JENKINS-27288) Leaking temporary directories named /tmp/hudson*tmp
Cristian Magherusan-Stanciu created JENKINS-27288 Leaking temporary directories named /tmp/hudson*tmp Issue Type: Bug Assignee: Vincent Latombe Components: pollscm-plugin Created: 09/Mar/15 10:56 AM Description: I just noticed that the SCM polling failed for all of our builds because no temporary files could be created in /tmp. When looking there, I saw there were some 32k files named like hudson2195781228286547025tmp and that I'm hitting a filesystem limit that only allows a directory to have up to 32K files. I deleted them all but they keep reappearing. $ ls -la /tmp | grep hudson| wc -l 8 $ ls -la /tmp | grep hudson| wc -l 28 $ ls -la /tmp | grep hudson| wc -l 42 Environment: - jenkins 1.599 - CentOS Linux 6.5 - ext3 filesystem Project: Jenkins Priority: Major Reporter: Cristian Magherusan-Stanciu 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] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
Cristian Magherusan-Stanciu commented on JENKINS-26572 Log Parser incompatible with Jenkins 1.597 (build record change) I'm also impacted by this, and indeed the latest build from source works on 1.599. Who could officially release a new version of this plugin? 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] [jenkinswalldisplay] (JENKINS-13992) Sort jobs by name or by priority or by downstream
Cristian Magherusan-Stanciu commented on JENKINS-13992 Sort jobs by name or by priority or by downstream Are there any updates on this issue? I also set a symbolic 10$ bounty for it on http://freedomsponsors.org/core/issue/414 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/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
Cristian Magherusan-Stanciu edited a comment on JENKINS-17029 update-center.json seems to be broken It is happening now once again. hudson.model.UpdateSite updateData SEVERE: ERROR: Digest mismatch: vCzo4VShUNOq+D3L/OhKVMzF0ms= vs RbxnYzSwuJIFmMJJSZ4RqZI6vdQ= in update site default I am having this problem on a new Jenkins installation and I can't install any plugins. I also have an older install with the same issue, but there I already have the plugins that I need already installed. I wish there was a way to override this check without recompiling Jenkins, through the settings. 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/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
Cristian Magherusan-Stanciu commented on JENKINS-17029 update-center.json seems to be broken It is happening now once again. hudson.model.UpdateSite updateData SEVERE: ERROR: Digest mismatch: vCzo4VShUNOq+D3L/OhKVMzF0ms= vs RbxnYzSwuJIFmMJJSZ4RqZI6vdQ= in update site default Is there a way to override this check? I am having this problem on a new Jenkins installation and I can't install any plugins. I also have an older install with the same issue, but there I already have the plugins that I need already installed. 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/groups/opt_out.
