[JIRA] (JENKINS-13928) bad version number at offiset=6
[ https://issues.jenkins-ci.org/browse/JENKINS-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163463#comment-163463 ] Carl Chen commented on JENKINS-13928: - i removed old plugin from %HOME%/.jenkins/plugins/clearcase-ucm-plugin* and then restart my tomcat. next step is to find new plugin 1.1.0 and install it. but failed again. my os is windows xp, tomcat 6.0.35, jenkins 1.461. see below error INFO: Augmented all extensions Jun 4, 2012 10:19:51 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout net.praqma.hudson.notifier.CCUCMNotifier$DescriptorImpl java.lang.InstantiationException: file:/C:/Documents%20and%20Settings/e464150/.jenkins/plugins/clearcase-ucm-plugin/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: net.praqma.hudson.notifier.CCUCMNotifier$DescriptorImpl at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:644) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:283) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:839) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassNotFoundException: net.praqma.hudson.notifier.CCUCMNotifier$DescriptorImpl at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:767) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 24 more Jun 4, 2012 10:19:51 AM hudson.ExtensionFinder$Sezpoz scout > bad version number at offiset=6 > --- > > Key: JENKINS-13928 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13928 > Project: Jenkins > Issue Type: Bug > Components: clearcase-ucm >Affects Versions: current > Environment: windows xp , tomcat 6.0.35, jenkins 1.465, > clearcase-ucm-plugin 1.0.7 >Reporter: Carl Chen >Assignee: Christian Wolfgang > Labels: plugin > > jenkins runs well, but after install this plugin, it reports bad version > number error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13924) Very inefficiently deleting CloudFormation stack
[ https://issues.jenkins-ci.org/browse/JENKINS-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damon Evans updated JENKINS-13924: -- Attachment: fixed-jenkins-cloudformation-plugin.patch Fixed patch. The original one didn't handle the exception that was thrown (I had confused it with the ListStacks call). > Very inefficiently deleting CloudFormation stack > > > Key: JENKINS-13924 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13924 > Project: Jenkins > Issue Type: Patch > Components: cloudformation, jenkins-cloudformation >Affects Versions: current > Environment: All environments. >Reporter: Damon Evans >Assignee: edovale > Fix For: current > > Attachments: fixed-jenkins-cloudformation-plugin.patch, > jenkins-cloudformation-plugin.patch > > > When waiting for the CloudFormation stack to delete, the method is calling > DescribeStacks without passing in a StackName. This results in a call that > will get all the information about all stacks, not just the one we are > waiting for. This adds a lot of time to call. By simply adding the name into > the call, we make a much lighter and faster call. This was already done while > waiting for the stack to create. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13793) Build isn't triggered after reboot
[ https://issues.jenkins-ci.org/browse/JENKINS-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163461#comment-163461 ] Gregory Boissinot commented on JENKINS-13793: - It is an issue that the plugin has to be take care. You're right, there is no change detection because Jenkins has reboot and the plugin uses only persistence in memory at the moment. I need to add a feature to have persistence on demand for this plugin. > Build isn't triggered after reboot > -- > > Key: JENKINS-13793 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13793 > Project: Jenkins > Issue Type: Bug > Components: buildresult-trigger > Environment: Mac OS X Jenkins 1.463 buildresult-trigger 0.6 >Reporter: Alan Birtles >Priority: Minor > > After rebooting jenkins the buildresult-trigger won't trigger a build. > In our setup we use the buildresult-trigger to run a nightly test suite only > after a build has happened during the day. > If the server is rebooted then builds will not be triggered on the first > night and will only be triggered on the second night if another build has > happened during the second day. > The polling log on the first night says that the monitored build didn't exist > before. I guess this is because the plugin has no persistance? This means > that after installing updates or new plugins our tests wont run for at least > a day. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13793) Build isn't triggered after reboot
[ https://issues.jenkins-ci.org/browse/JENKINS-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Build isn't triggered after reboot > -- > > Key: JENKINS-13793 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13793 > Project: Jenkins > Issue Type: Bug > Components: buildresult-trigger > Environment: Mac OS X Jenkins 1.463 buildresult-trigger 0.6 >Reporter: Alan Birtles >Priority: Minor > > After rebooting jenkins the buildresult-trigger won't trigger a build. > In our setup we use the buildresult-trigger to run a nightly test suite only > after a build has happened during the day. > If the server is rebooted then builds will not be triggered on the first > night and will only be triggered on the second night if another build has > happened during the second day. > The polling log on the first night says that the monitored build didn't exist > before. I guess this is because the plugin has no persistance? This means > that after installing updates or new plugins our tests wont run for at least > a day. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13747) Jira Jenkins components "buildresult-trigger" and "buildresulttrigger" should be merged
[ https://issues.jenkins-ci.org/browse/JENKINS-13747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Boissinot updated JENKINS-13747: Priority: Minor (was: Major) Description: The two Jira Jenkins components "buildresult-trigger" and "buildresulttrigger" obviously represent the same thing, so should be merged. was:The two Jira Jenkins components "buildresult-trigger" and "buildresulttrigger" obviously represent the same thing, so should be merged It is a minor issue. > Jira Jenkins components "buildresult-trigger" and "buildresulttrigger" should > be merged > --- > > Key: JENKINS-13747 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13747 > Project: Jenkins > Issue Type: Task > Components: buildresult-trigger, buildresulttrigger >Reporter: mwebber >Assignee: Gregory Boissinot >Priority: Minor > > The two Jira Jenkins components "buildresult-trigger" and > "buildresulttrigger" obviously represent the same thing, so should be merged. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2460) Allow branch option on cvs tag
[ https://issues.jenkins-ci.org/browse/JENKINS-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-2460. --- Resolution: Fixed > Allow branch option on cvs tag > -- > > Key: JENKINS-2460 > URL: https://issues.jenkins-ci.org/browse/JENKINS-2460 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: gdlloyd >Assignee: Michael Clarke > > Please could you add the enhancement to select (tick box perhaps?) rather > create > a cvs branch when selecting the build option "Tag this build". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2460) Allow branch option on cvs tag
[ https://issues.jenkins-ci.org/browse/JENKINS-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163459#comment-163459 ] SCM/JIRA link daemon commented on JENKINS-2460: --- Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/cvstagging/CvsTagAction.java src/main/java/hudson/scm/cvstagging/CvsTagActionWorker.java src/main/resources/hudson/scm/cvstagging/CvsTagAction/tagForm.jelly http://jenkins-ci.org/commit/cvs-plugin/8393a3f109c47253cad7f24fae6cd8cc728caded Log: [FIXED JENKINS-2460] Allow branching on (non legacy) tag action > Allow branch option on cvs tag > -- > > Key: JENKINS-2460 > URL: https://issues.jenkins-ci.org/browse/JENKINS-2460 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: gdlloyd >Assignee: Michael Clarke > > Please could you add the enhancement to select (tick box perhaps?) rather > create > a cvs branch when selecting the build option "Tag this build". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163458#comment-163458 ] SCM/JIRA link daemon commented on JENKINS-13007: Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitAPI.java http://jenkins-ci.org/commit/git-plugin/db53ccea4188e182336f5e5c579f6adce34f6ecb Log: Merge pull request #71 from vjuranek/JENKINS-13007 [FIXED JENKINS-13007] Handle special meaning of some charactes on Window... Compare: https://github.com/jenkinsci/git-plugin/compare/cef9941...db53cce > Git plugin cannot find revision to build on Windows > --- > > Key: JENKINS-13007 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 > Project: Jenkins > Issue Type: Bug > Components: git > Environment: Windows 2008 Server 64 Bit > NTFS >Reporter: ritzmann >Assignee: Nicolas De Loof >Priority: Critical > > After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on > Windows build slaves started failing like this: > Started by user anonymous > Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app > Checkout:my-app / d:\hudson\workspace\my-app - > hudson.remoting.Channel@95ff886:win-slave1 > Using strategy: Default > Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 > (origin/master) > Checkout:my-app / d:\hudson\workspace\my-app - > hudson.remoting.LocalChannel@470a4b80 > Fetching changes from 1 remote Git repository > Fetching upstream changes from d:\hudson\shared\repo.git > ERROR: Couldn't find any revision to build. Verify the repository and branch > configuration for this job. > The builds on our Linux slaves are not affected. Wiping the workspaces on the > Windows slaves did not help. Both clones and checkouts/updates seem to fail > with the same error. Downgrading back to 1.1.14 made the Windows builds work > again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13007. Resolution: Fixed > Git plugin cannot find revision to build on Windows > --- > > Key: JENKINS-13007 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 > Project: Jenkins > Issue Type: Bug > Components: git > Environment: Windows 2008 Server 64 Bit > NTFS >Reporter: ritzmann >Assignee: Nicolas De Loof >Priority: Critical > > After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on > Windows build slaves started failing like this: > Started by user anonymous > Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app > Checkout:my-app / d:\hudson\workspace\my-app - > hudson.remoting.Channel@95ff886:win-slave1 > Using strategy: Default > Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 > (origin/master) > Checkout:my-app / d:\hudson\workspace\my-app - > hudson.remoting.LocalChannel@470a4b80 > Fetching changes from 1 remote Git repository > Fetching upstream changes from d:\hudson\shared\repo.git > ERROR: Couldn't find any revision to build. Verify the repository and branch > configuration for this job. > The builds on our Linux slaves are not affected. Wiping the workspaces on the > Windows slaves did not help. Both clones and checkouts/updates seem to fail > with the same error. Downgrading back to 1.1.14 made the Windows builds work > again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163457#comment-163457 ] SCM/JIRA link daemon commented on JENKINS-13007: Code changed in jenkins User: Vojtech Juranek Path: src/main/java/hudson/plugins/git/GitAPI.java http://jenkins-ci.org/commit/git-plugin/938ca81a991b1175d58fbcbb96b5efe37ab2f9a6 Log: [FIXED JENKINS-13007] Handle special meaning of some charactes on Windows > Git plugin cannot find revision to build on Windows > --- > > Key: JENKINS-13007 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 > Project: Jenkins > Issue Type: Bug > Components: git > Environment: Windows 2008 Server 64 Bit > NTFS >Reporter: ritzmann >Assignee: Nicolas De Loof >Priority: Critical > > After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on > Windows build slaves started failing like this: > Started by user anonymous > Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app > Checkout:my-app / d:\hudson\workspace\my-app - > hudson.remoting.Channel@95ff886:win-slave1 > Using strategy: Default > Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 > (origin/master) > Checkout:my-app / d:\hudson\workspace\my-app - > hudson.remoting.LocalChannel@470a4b80 > Fetching changes from 1 remote Git repository > Fetching upstream changes from d:\hudson\shared\repo.git > ERROR: Couldn't find any revision to build. Verify the repository and branch > configuration for this job. > The builds on our Linux slaves are not affected. Wiping the workspaces on the > Windows slaves did not help. Both clones and checkouts/updates seem to fail > with the same error. Downgrading back to 1.1.14 made the Windows builds work > again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13925) After upgrade the groupChats info is null and results in a nullpointer exception preventing the plugin from working
[
https://issues.jenkins-ci.org/browse/JENKINS-13925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-13925.
Resolution: Fixed
> After upgrade the groupChats info is null and results in a nullpointer
> exception preventing the plugin from working
> ---
>
> Key: JENKINS-13925
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13925
> Project: Jenkins
> Issue Type: Bug
> Components: jabber
>Affects Versions: current
>Reporter: Ruben Garat
>Assignee: kutzi
>
> After upgrading jenkins (1.432 to 1.465), the instant-messenger (to 1.21)
> plugin and the jabber (to 1.22) plugin the jabber comunication (using google
> talk) stopped working, and started throwing a null pointer exception.
> {noformat}
> May 26, 2012 6:46:53 PM hudson.plugins.jabber.im.transport.JabberIMConnection
> connect
> INFO: Connected to XMPP on talk.google.com:5222/gmail.com using TLS
> May 26, 2012 6:46:53 PM hudson.plugins.jabber.im.transport.JabberIMConnection
> connect
> WARNING: java.lang.NullPointerException
> at
> hudson.plugins.jabber.im.transport.JabberIMConnection.connect(JabberIMConnection.java:166)
> at
> hudson.plugins.jabber.im.transport.JabberIMConnectionProvider.createConnection(JabberIMConnectionProvider.java:42)
> at
> hudson.plugins.im.IMConnectionProvider.create(IMConnectionProvider.java:65)
> at
> hudson.plugins.im.IMConnectionProvider.access$600(IMConnectionProvider.java:22)
> at
> hudson.plugins.im.IMConnectionProvider$ConnectorRunnable.run(IMConnectionProvider.java:183)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> In the 1.22 version of the jabber plugin the line where the nullpointer
> occurs is
> {code:title=hudson.plugins.jabber.im.transport.JabberIMConnection.java|borderStyle=solid}
> for (IMMessageTarget chat : this.groupChats) {
> {code}
> In the previous version of the jabber plugin I didn´t have any groupChat
> defined, so I thought that maybe there was some problem updating that
> configuration so I:
> * configured a fake group chat
> * saved and restarted (this gave an error that it couldn´t use the groupchat
> obviously)
> * removed the fake group chat
> * saved and restarted (now the nullpointer error stopped and everything works
> fine)
> In the end I think that the fix should be either handling the possibility of
> a null groupchat list or detecting that and fixing the configuration before
> attempting to connect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13925) After upgrade the groupChats info is null and results in a nullpointer exception preventing the plugin from working
[
https://issues.jenkins-ci.org/browse/JENKINS-13925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163456#comment-163456
]
SCM/JIRA link daemon commented on JENKINS-13925:
Code changed in jenkins
User: Christoph Kutzinski
Path:
src/main/java/hudson/plugins/jabber/im/transport/JabberPublisherDescriptor.java
http://jenkins-ci.org/commit/jabber-plugin/da69c972a35c75542a0745d70d6807bac1708950
Log:
[FIXED JENKINS-13925] fixed NPE if no groupChats were configured, previously
> After upgrade the groupChats info is null and results in a nullpointer
> exception preventing the plugin from working
> ---
>
> Key: JENKINS-13925
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13925
> Project: Jenkins
> Issue Type: Bug
> Components: jabber
>Affects Versions: current
>Reporter: Ruben Garat
>Assignee: kutzi
>
> After upgrading jenkins (1.432 to 1.465), the instant-messenger (to 1.21)
> plugin and the jabber (to 1.22) plugin the jabber comunication (using google
> talk) stopped working, and started throwing a null pointer exception.
> {noformat}
> May 26, 2012 6:46:53 PM hudson.plugins.jabber.im.transport.JabberIMConnection
> connect
> INFO: Connected to XMPP on talk.google.com:5222/gmail.com using TLS
> May 26, 2012 6:46:53 PM hudson.plugins.jabber.im.transport.JabberIMConnection
> connect
> WARNING: java.lang.NullPointerException
> at
> hudson.plugins.jabber.im.transport.JabberIMConnection.connect(JabberIMConnection.java:166)
> at
> hudson.plugins.jabber.im.transport.JabberIMConnectionProvider.createConnection(JabberIMConnectionProvider.java:42)
> at
> hudson.plugins.im.IMConnectionProvider.create(IMConnectionProvider.java:65)
> at
> hudson.plugins.im.IMConnectionProvider.access$600(IMConnectionProvider.java:22)
> at
> hudson.plugins.im.IMConnectionProvider$ConnectorRunnable.run(IMConnectionProvider.java:183)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> In the 1.22 version of the jabber plugin the line where the nullpointer
> occurs is
> {code:title=hudson.plugins.jabber.im.transport.JabberIMConnection.java|borderStyle=solid}
> for (IMMessageTarget chat : this.groupChats) {
> {code}
> In the previous version of the jabber plugin I didn´t have any groupChat
> defined, so I thought that maybe there was some problem updating that
> configuration so I:
> * configured a fake group chat
> * saved and restarted (this gave an error that it couldn´t use the groupchat
> obviously)
> * removed the fake group chat
> * saved and restarted (now the nullpointer error stopped and everything works
> fine)
> In the end I think that the fix should be either handling the possibility of
> a null groupchat list or detecting that and fixing the configuration before
> attempting to connect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9309) sloccount trend report only works up to last failed build
[ https://issues.jenkins-ci.org/browse/JENKINS-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-9309 started by Karsten Brandt. > sloccount trend report only works up to last failed build > - > > Key: JENKINS-9309 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9309 > Project: Jenkins > Issue Type: Bug > Components: sloccount >Reporter: Johannes Wienke >Assignee: Karsten Brandt > > The rend report generated by the sloccount plugin is destroyed by failing > builds. The trend report only displays the results up to the last failing > build. This reduces the usefulness of the report as no general view over the > whole project life time is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9309) sloccount trend report only works up to last failed build
[ https://issues.jenkins-ci.org/browse/JENKINS-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karsten Brandt reassigned JENKINS-9309: --- Assignee: Karsten Brandt (was: npiguet) > sloccount trend report only works up to last failed build > - > > Key: JENKINS-9309 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9309 > Project: Jenkins > Issue Type: Bug > Components: sloccount >Reporter: Johannes Wienke >Assignee: Karsten Brandt > > The rend report generated by the sloccount plugin is destroyed by failing > builds. The trend report only displays the results up to the last failing > build. This reduces the usefulness of the report as no general view over the > whole project life time is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14001) Jabber plugin cannot be installed without maven plugin
[
https://issues.jenkins-ci.org/browse/JENKINS-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kutzi updated JENKINS-14001:
Component/s: core
> Jabber plugin cannot be installed without maven plugin
> --
>
> Key: JENKINS-14001
> URL: https://issues.jenkins-ci.org/browse/JENKINS-14001
> Project: Jenkins
> Issue Type: Bug
> Components: core, jabber
> Environment: Jenkins 1.447 installed from Debian testing package,
> Jabber 1.22, Instant-messaging 1.21.
>Reporter: Tomasz Melcer
>Assignee: kutzi
>
> I couldn't install instant-messaging and jabber plugins on a fresh
> installation on Jenkins. After installing them and restarting Jenkins, the
> only visual clue I got was that those plugins were not on the installed
> plugins list.
> Digging into the log I found:
> {noformat}
> WARNING: Adding dependent install of instant-messaging for plugin jabber
> [...]
> SEVERE: Failed Loading plugin instant-messaging
> java.io.IOException: Dependency maven-plugin (1.392) doesn't exist
> at
> hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:434)
> at hudson.PluginManager$2$1$1.run(PluginManager.java:293)
> at
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
> at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
> at jenkins.model.Jenkins$5.runTask(Jenkins.java:799)
> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
> at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> May 31, 2012 3:41:49 PM jenkins.InitReactorRunner$1 onTaskFailed
> SEVERE: Failed Loading plugin jabber
> java.io.IOException: Dependency maven-plugin (1.392), instant-messaging
> (1.21) doesn't exist
> at
> hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:434)
> at hudson.PluginManager$2$1$1.run(PluginManager.java:293)
> at
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
> at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
> at jenkins.model.Jenkins$5.runTask(Jenkins.java:799)
> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
> at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> [...]
> SEVERE: Failed to install Instant Messaging Plugin
> hudson.util.IOException2: Failed to dynamically deploy this plugin
> at
> hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
> at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: hudson.util.IOException2: Failed to install instant-messaging
> plugin
> at hudson.PluginManager.dynamicLoad(PluginManager.java:365)
> at
> hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
> ... 7 more
> Caused by: java.io.IOException: Dependency maven-plugin (1.392) doesn't exist
> at
> hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:434)
> at hudson.PluginManager.dynamicLoad(PluginManager.java:355)
> ... 8 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14001) Jabber plugin cannot be installed without maven plugin
Tomasz Melcer created JENKINS-14001:
---
Summary: Jabber plugin cannot be installed without maven plugin
Key: JENKINS-14001
URL: https://issues.jenkins-ci.org/browse/JENKINS-14001
Project: Jenkins
Issue Type: Bug
Components: jabber
Environment: Jenkins 1.447 installed from Debian testing package,
Jabber 1.22, Instant-messaging 1.21.
Reporter: Tomasz Melcer
Assignee: kutzi
I couldn't install instant-messaging and jabber plugins on a fresh installation
on Jenkins. After installing them and restarting Jenkins, the only visual clue
I got was that those plugins were not on the installed plugins list.
Digging into the log I found:
{noformat}
WARNING: Adding dependent install of instant-messaging for plugin jabber
[...]
SEVERE: Failed Loading plugin instant-messaging
java.io.IOException: Dependency maven-plugin (1.392) doesn't exist
at
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:434)
at hudson.PluginManager$2$1$1.run(PluginManager.java:293)
at
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:799)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
May 31, 2012 3:41:49 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin jabber
java.io.IOException: Dependency maven-plugin (1.392), instant-messaging (1.21)
doesn't exist
at
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:434)
at hudson.PluginManager$2$1$1.run(PluginManager.java:293)
at
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:799)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
[...]
SEVERE: Failed to install Instant Messaging Plugin
hudson.util.IOException2: Failed to dynamically deploy this plugin
at
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: hudson.util.IOException2: Failed to install instant-messaging plugin
at hudson.PluginManager.dynamicLoad(PluginManager.java:365)
at
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
... 7 more
Caused by: java.io.IOException: Dependency maven-plugin (1.392) doesn't exist
at
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:434)
at hudson.PluginManager.dynamicLoad(PluginManager.java:355)
... 8 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13706) Jabber/IRCBot credentials stored in clear text
[
https://issues.jenkins-ci.org/browse/JENKINS-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kutzi resolved JENKINS-13706.
-
Resolution: Fixed
> Jabber/IRCBot credentials stored in clear text
> --
>
> Key: JENKINS-13706
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13706
> Project: Jenkins
> Issue Type: Bug
> Components: ircbot, jabber
>Affects Versions: current
>Reporter: Julien R.
>Assignee: kutzi
>Priority: Minor
> Labels: jabber, password
>
> If you open hudson.plugins.jabber.im.transport.JabberPublisher.xml you will
> notice that the jabber password is stored in cleartext :
> {code:xml}
>
> [...]
> Protext_the_innocent
> {code}
> Other components (ldap bind password, svn) have a hash mechanism as far as I
> can see, not sure if there is a common library to use but it would be a nice
> addition.
> Thank you !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13706) Jabber/IRCBot credentials stored in clear text
[
https://issues.jenkins-ci.org/browse/JENKINS-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163455#comment-163455
]
SCM/JIRA link daemon commented on JENKINS-13706:
Code changed in jenkins
User: Christoph Kutzinski
Path:
pom.xml
src/main/java/hudson/plugins/jabber/im/transport/JabberPublisherDescriptor.java
http://jenkins-ci.org/commit/jabber-plugin/d1515ae837d00be74e97882e10dfcbd6077f1b83
Log:
Save password scrambled [JENKINS-13706]
> Jabber/IRCBot credentials stored in clear text
> --
>
> Key: JENKINS-13706
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13706
> Project: Jenkins
> Issue Type: Bug
> Components: ircbot, jabber
>Affects Versions: current
>Reporter: Julien R.
>Assignee: kutzi
>Priority: Minor
> Labels: jabber, password
>
> If you open hudson.plugins.jabber.im.transport.JabberPublisher.xml you will
> notice that the jabber password is stored in cleartext :
> {code:xml}
>
> [...]
> Protext_the_innocent
> {code}
> Other components (ldap bind password, svn) have a hash mechanism as far as I
> can see, not sure if there is a common library to use but it would be a nice
> addition.
> Thank you !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13706) Jabber/IRCBot credentials stored in clear text
[
https://issues.jenkins-ci.org/browse/JENKINS-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163454#comment-163454
]
SCM/JIRA link daemon commented on JENKINS-13706:
Code changed in jenkins
User: Christoph Kutzinski
Path:
pom.xml
src/main/java/hudson/plugins/ircbot/IrcPublisher.java
http://jenkins-ci.org/commit/ircbot-plugin/cbe23a16db65a2e857ff5f5404a37b61192ffbc2
Log:
Save passwords scrambled [JENKINS-13706]
> Jabber/IRCBot credentials stored in clear text
> --
>
> Key: JENKINS-13706
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13706
> Project: Jenkins
> Issue Type: Bug
> Components: ircbot, jabber
>Affects Versions: current
>Reporter: Julien R.
>Assignee: kutzi
>Priority: Minor
> Labels: jabber, password
>
> If you open hudson.plugins.jabber.im.transport.JabberPublisher.xml you will
> notice that the jabber password is stored in cleartext :
> {code:xml}
>
> [...]
> Protext_the_innocent
> {code}
> Other components (ldap bind password, svn) have a hash mechanism as far as I
> can see, not sure if there is a common library to use but it would be a nice
> addition.
> Thank you !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163453#comment-163453 ] Michael Clarke commented on JENKINS-12598: -- This has been included in Version 2.4 of the plugin. I'll look at how we can add a text box in during a future release (probably 2.6) without cluttering the interface or confusing users. If you're desperate for it then raise another issue so it remains on my todo list. > In 2.0 update you need to specify branch for every module > - > > Key: JENKINS-12598 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12598 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Reporter: Ulli Hafner >Assignee: Michael Clarke >Priority: Critical > Attachments: Jenkins_CvsPluginModules.png, > repositoryLocationProposal.png > > > After an upgrade to the new 2.0 version of the cvs plug-in we now need to > specify the "Module location" (trunk, branch) for each module. This is quite > cumbersome if you have a lot of modules. In the 1.x plug-in releases you are > able to select a given branch for all modules in one text field. > While I think the new "feature" has a lot of use cases (i.e., having trunk > and branches mixed), the usability could be improved here. My requirement is > to select/change the branch (or trunk) for all modules in a simple way. > A non-Ajax suggestion would be to have a "default" entry in the Selection, > i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at > the top of the cvs configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13439) Tagging a build fails due to exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke resolved JENKINS-13439. -- Resolution: Fixed Release in version 2.4 of Cvs Plugin > Tagging a build fails due to exception > -- > > Key: JENKINS-13439 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13439 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: Jeknins 1.458 > CVS-Plugin 2.2 > Windows Server 2008 >Reporter: Roland Benning >Assignee: Michael Clarke > Labels: plugin > > Whenever I want to tag a build I get an error (see below). I am using Jeknins > 1.458 ans CVS-Plugin 2.2. Do you have any suggestions? > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) > at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) > at > org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) > at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) > at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) > at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) > at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) > at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485) > at org.kohsuke.stapler.Stapler.service(Stapler.java:159) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) > at > hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) > at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) > at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) > at > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > at > hudson.security.ChainedServletFilter$1.doFilter
[JIRA] (JENKINS-13706) Jabber/IRCBot credentials stored in clear text
[
https://issues.jenkins-ci.org/browse/JENKINS-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kutzi updated JENKINS-13706:
Summary: Jabber/IRCBot credentials stored in clear text (was: Config
stored jabber credential in clear text)
Component/s: ircbot
> Jabber/IRCBot credentials stored in clear text
> --
>
> Key: JENKINS-13706
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13706
> Project: Jenkins
> Issue Type: Bug
> Components: ircbot, jabber
>Affects Versions: current
>Reporter: Julien R.
>Assignee: kutzi
>Priority: Minor
> Labels: jabber, password
>
> If you open hudson.plugins.jabber.im.transport.JabberPublisher.xml you will
> notice that the jabber password is stored in cleartext :
> {code:xml}
>
> [...]
> Protext_the_innocent
> {code}
> Other components (ldap bind password, svn) have a hash mechanism as far as I
> can see, not sure if there is a common library to use but it would be a nice
> addition.
> Thank you !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12333) OOME/PermGen
[
https://issues.jenkins-ci.org/browse/JENKINS-12333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kutzi resolved JENKINS-12333.
-
Resolution: Incomplete
Closing as incomplete. Please reopen if you have more information available.
> OOME/PermGen
>
>
> Key: JENKINS-12333
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12333
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Debian, 64-bit, 16 GB RAM, 8 processors.
> Jenkins running in Jetty with JAVA_OPTIONS="-Xmx640m -XX:MaxPermSize=128m"
> ~250-300 jobs
>Reporter: carlspring
>Priority: Blocker
> Labels: memory-leak
>
> The other day I upgraded from Jenkins 1.413 to 1.446. I migrated the data
> which it reported as old to the new format and upgraded the plugins
> respectively. All seemed to work fine. Then all of a sudden within an hour or
> so we hit:
> {code}
> Exception in thread "Ping thread for channel
> hudson.remoting.Channel@5d1dce7a:bud" java.lang.OutOfMemoryError: Java heap
> space
> Exception in thread "Thread-109599" java.lang.OutOfMemoryError: Java heap
> space
> Jan 8, 2012 12:10:19 PM hudson.triggers.SafeTimerTask run
> SEVERE: Timer task hudson.diagnosis.MemoryUsageMonitor@3b9e30a1 failed
> java.lang.OutOfMemoryError: Java heap space
> at hudson.model.TimeSeries.update(TimeSeries.java:74)
> at
> hudson.model.MultiStageTimeSeries.update(MultiStageTimeSeries.java:118)
> at
> hudson.diagnosis.MemoryUsageMonitor$MemoryGroup.update(MemoryUsageMonitor.java:95)
> at
> hudson.diagnosis.MemoryUsageMonitor$MemoryGroup.access$100(MemoryUsageMonitor.java:54)
> at
> hudson.diagnosis.MemoryUsageMonitor.doRun(MemoryUsageMonitor.java:123)
> at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> 2012-01-08 12:25:06.254:WARN::Problem scavenging sessions
> java.lang.OutOfMemoryError: Java heap space
> {code}
> We have the following setup:
> - Linux master (6 executors)
> - 2 linux nodes (4 executors + 8 executors)
> - 2 windows nodes (both running 4 executors)
> We have 250-300 jobs. 90% of them are also producing Sonar reports.
> This totally crashes Jenkins and it is unreachable after the OOME/PermGen.
> Jenkins is running inside a Jetty.
> After hitting this problem, I tried increasing the memory settings of Jetty
> (which was working fine without any memory settings back in 1.413) to:
> JAVA_OPTIONS="-Xmx640m -XX:MaxPermSize=128m"
> This seemed to work. Until it became apparent that it only slowed the
> re-occurrence of the problem.
> So, I started jstatd and connected via visualvm and saw:
> Permgen: 128m / 90m used.
> OldGen: 426.6m / 426.6 m used
> Please, fix as it's a blocker for us and I now have to resort to rolling back
> to our last know good version, i.e. 1.413.
> Thanks in advance for looking into this! :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
