[JIRA] (JENKINS-13498) certificate used to sign update list is expired
[ https://issues.jenkins-ci.org/browse/JENKINS-13498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Revelut closed JENKINS-13498. - Confirmed it's working, closing certificate used to sign update list is expired --- Key: JENKINS-13498 URL: https://issues.jenkins-ci.org/browse/JENKINS-13498 Project: Jenkins Issue Type: Bug Components: core Environment: Latest jenkins for windows Reporter: Florent Revelut Priority: Blocker Labels: update, website, x509 Fix For: current Attachments: DecodedBase64.bin trying to update list of plugins from http://mirrors.karan.org/jenkins/updates/update-center.json Provides a signing certificate : MIIDezCCAmMCBQDerb7wMA0GCSqGSIb3DQEBBAUAMIGKMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTERMA8GA1UEBxMIU2FuIEpvc2UxGDAWBgNVBAoTD0plbmtpbnMgUHJvamVjdDEaMBgGA1UEAxMRS29oc3VrZSBLYXdhZ3VjaGkxHTAbBgkqhkiG9w0BCQEWDmtrQGtvaHN1a2Uub3JnMB4XDTExMDQxOTA3MzUwNFoXDTEyMDQxODA3MzUwNFoweDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExGDAWBgNVBAoTD0plbmtpbnMgUHJvamVjdDEeMBwGA1UECxMVRGVmYXVsdCBVcGRhdGUgQ2VudGVyMRowGAYDVQQDExFLb2hzdWtlIEthd2FndWNoaTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANRDu439lC/Ie+LlQ42vYICZZ9aIA8+poXhJLt1Mhosz+zFGCdljWTvO3/wxNx7uA053YTIKu73cSAxVjWK8Qfhv19hKXNKe7wvHZF0y6VbSKqKctjXsm/4nWrGr61FTIxr3LcM3byx/vJ0tykQmiDc5/oov7MmUpBLSg1yCyO70t1/NxyYy7xCreU2G1x2w+RxFakfIaLK9r33FcFH+mrEzQZHxoxlg3AuLn1WDz9+mRMvCEEZU6AQh07gBG8f8dOV9ot2vaknkF+w4OTsDdUdXY5sNghr6yQTLU8++0u/f9N8j+cP07C39OWnIjloBt3WVuhSuw83IqOJHoYh85wUCAwEAATANBgkqhkiG9w0BAQQFAAOCAQEAfAte7k2JdwxS32FkJLj6i81wDaI8EUGoN2sbTRgFs/nXMxG1RuboPRLbz63IL/eRBvcUbq1RD+7UnrFjDkmN8SQlN90w3ODobOJv3U1zaJ01ehNa3CRgsCcIRjITtSWD+b2132rR9G2a7ZXD8GQ+50QhkG6SVwPwo/mklkleRb5WTcSCKrmHvZPsxCtrMSbw6OL1dM9h0j8vLaIMpxkCoJotajsTjP94LfP4z1JU4ifXaC/uXdugoQ9t6+0n+qrsYdI4JHV9OI5nMEJ5bdhvxAzA8enj/hZ9i/lekoUurc2W87dHdO46Kyt1PjCYS4LGVRsjeh04cCocajIVL2zM0w== Once dumped : Certificate: Data: Version: 1 (0x0) Serial Number: 3735928560 (0xdeadbef0) Signature Algorithm: md5WithRSAEncryption Issuer: C=US, ST=California, L=San Jose, O=Jenkins Project, CN=Kohsuke Kawaguchi/emailAddress=k...@kohsuke.org Validity Not Before: Apr 19 07:35:04 2011 GMT Not After : Apr 18 07:35:04 2012 GMT Subject: C=US, ST=California, O=Jenkins Project, OU=Default Update Center, CN=Kohsuke Kawaguchi = certificate expired this morning. this leads to the following exception when trying to refresh plugins list: 18 avr. 2012 15:28:23 hudson.model.UpdateSite doPostBack GRAVE: div class=errorimg src='/static/10b6d8c8/images/none.gif' height=16 width=1Signature verification failed in the update center #039;default#039; a href='#' class='showDetails'(show details)/apre style='display:none'java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(Unknown Source) at sun.security.provider.certpath.PKIXCertPathValidator.doValidate(Unknown Source) (zip) = certificate should be renewed = as a workaround, we could be able to bypass signature validation -- 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-13872) Counter Parameter Factory
[ https://issues.jenkins-ci.org/browse/JENKINS-13872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacobo Jimenez updated JENKINS-13872: - Due Date: (was: 18/May/12) Counter Parameter Factory - Key: JENKINS-13872 URL: https://issues.jenkins-ci.org/browse/JENKINS-13872 Project: Jenkins Issue Type: Bug Components: parameterized-trigger Affects Versions: current Environment: GNU/Linux x86_64 2.6.16 Tomcat Reporter: Jacobo Jimenez Assignee: huybrechts Labels: builds, exception, parallel, parameterized, trigger Defining a Trigger/call builds on other projects build step with Counter Parameter Factory as follow: FROM = 1 TO = $VARIABLE STEP = 1 It should do nothing, I mean, do not build step, if $VARIABLE is zero but it is failing with following exception: FATAL: Counting with step size 0 will not terminate! java.lang.RuntimeException: Counting with step size 0 will not terminate! -- 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-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
[ https://issues.jenkins-ci.org/browse/JENKINS-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacobo Jimenez updated JENKINS-13871: - Due Date: (was: 18/May/12) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Key: JENKINS-13871 URL: https://issues.jenkins-ci.org/browse/JENKINS-13871 Project: Jenkins Issue Type: Bug Components: conditional-buildstep, parameterized-trigger, run-condition Affects Versions: current Environment: GNU/Linux x86_64 2.6.16.60-0.69.1-smp Tomcat Reporter: Jacobo Jimenez Assignee: domi Labels: diamond, exception, interlock, parallel, parameter, stuck Attachments: QueueInterlockTest_main#config.xml, QueueInterlockTest_subtask#config.xml Job A triggers a variable number of job B depending on a environment variable. It can be zero but since Counter Parameter Factory doesnt allow zero repetitions (Java exception) I had to include this step as a conditional build step. Job A must wait until the end of all B jobs so option Block until the triggered projects finish their builds is selected (because it is really a diamond execution). This jobs configuration works fine but if you launch another A (in parallel) when it finish its first step and reach conditional step, it get stuck waiting until the end of all the jobs from first execution, once first A execution finished second execution continue executing its B jobs. This is a kind of interlocking process between executions. -- 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-13698) Error 500 on static assets with 1.463-1.1 rpm
[
https://issues.jenkins-ci.org/browse/JENKINS-13698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Doliner resolved JENKINS-13698.
Resolution: Fixed
Yep, the updated Green Balls plugin fixed the problem for us, too. Thanks!
Error 500 on static assets with 1.463-1.1 rpm
-
Key: JENKINS-13698
URL: https://issues.jenkins-ci.org/browse/JENKINS-13698
Project: Jenkins
Issue Type: Bug
Components: greenballs
Reporter: Mark Doliner
Assignee: asgeirn
Labels: exception
I yum updated to the jenkins-1.463-1.1 rpm from
http://pkg.jenkins-ci.org/redhat/ repository today at noon PDT. I'm running
on CentOS 5.8 with java 1.6.0.
Since then, logged out users get the following error response for various
static files (https://server:8443/static/5d0888f6/images/title.png, for
example):
{noformat}
May 7, 2012 1:39:38 PM winstone.Logger logInternal
WARNING: Untrapped Error in Servlet
java.lang.NullPointerException
at
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:50)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
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(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{noformat}
Interestingly, the error stops happening and the files are served
[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:comment-tabpanelfocusedCommentId=163216#comment-163216 ] Mathieu Bernatet commented on JENKINS-13439: Indeed, there is the same bug in LegacyTagAction. I've made a new pull request to fix this - https://github.com/jenkinsci/cvs-plugin/pull/13 . There is no remaining call on the method ListenerAndText.forMemory(Lhudson/model/TaskThread). 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
[JIRA] (JENKINS-13904) EnvInject Plugin: option to replace invalid characters in env var names with underscores
[
https://issues.jenkins-ci.org/browse/JENKINS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163217#comment-163217
]
Gregory Boissinot commented on JENKINS-13904:
-
Shell scripts have a wrong use for Environment variables with dot (.)
However, it is not the case for other languges and there are many connectors to
other languages with Jenkins.
I'm not sure that EnvInject has to be in charge of processing injected
environment variables.
I'm not completly agree to put processing for the EnvInject.
Why not to directly inject the correct environment variables?
EnvInject Plugin: option to replace invalid characters in env var names with
underscores
Key: JENKINS-13904
URL: https://issues.jenkins-ci.org/browse/JENKINS-13904
Project: Jenkins
Issue Type: New Feature
Components: envinject
Reporter: Chris Fraser
Assignee: Gregory Boissinot
Attachments: application.properties, envinject-with-new-option.jpg,
injected-environment-variables.jpg
I've got a Java properties file (example attached), which I don't have the
ability to modify, that I'm sourcing via EnvInject and this file contains
keys which are dot delimited (ex: app.version). EnvInject correctly pulls
these in as I've verified on the Injected environment variables screen, but
they are unresolvable when trying to use them in the job.
For instance, when trying to use ${app.version} w/the Git plugin to tag a
build, I get: Tag ${app.version}.4 does not exist..., and when I try to use
it when executing a shell, I get: ${app.version}: bad substitution. Keys
without dots from this same properties file work just fine... unfortunately I
need access to the ones w/the dots.
After doing a bit of research, I understand why this is happening.
1st of all, you have posted JIRA issues where kohsuke says that env vars
w/dots will not be expanded in Jenkins:
https://issues.jenkins-ci.org/browse/JENKINS-7180
Then, by doing a quick google search, you'll see that dots in env vars are
not supported in most shells and people say to just stay away from them.
With that in mind, I think a great feature to add to the EnvInject plugin
would be to give users the option to replace the dots (and actually any other
which are invalid in env var names) that appear in environment variable names
with an underscore. If you look at this issue that was opened against the
SharedObjects plugin, you'll see that, ...environment variables from tool
names replaces a space, a
dash or a dot to by a underscore.
https://issues.jenkins-ci.org/browse/JENKINS-13673
Please see attached properties files and screenshots.
--
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-13904) EnvInject Plugin: option to replace invalid characters in env var names with underscores
[
https://issues.jenkins-ci.org/browse/JENKINS-13904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-13904 started by Gregory Boissinot.
EnvInject Plugin: option to replace invalid characters in env var names with
underscores
Key: JENKINS-13904
URL: https://issues.jenkins-ci.org/browse/JENKINS-13904
Project: Jenkins
Issue Type: New Feature
Components: envinject
Reporter: Chris Fraser
Assignee: Gregory Boissinot
Attachments: application.properties, envinject-with-new-option.jpg,
injected-environment-variables.jpg
I've got a Java properties file (example attached), which I don't have the
ability to modify, that I'm sourcing via EnvInject and this file contains
keys which are dot delimited (ex: app.version). EnvInject correctly pulls
these in as I've verified on the Injected environment variables screen, but
they are unresolvable when trying to use them in the job.
For instance, when trying to use ${app.version} w/the Git plugin to tag a
build, I get: Tag ${app.version}.4 does not exist..., and when I try to use
it when executing a shell, I get: ${app.version}: bad substitution. Keys
without dots from this same properties file work just fine... unfortunately I
need access to the ones w/the dots.
After doing a bit of research, I understand why this is happening.
1st of all, you have posted JIRA issues where kohsuke says that env vars
w/dots will not be expanded in Jenkins:
https://issues.jenkins-ci.org/browse/JENKINS-7180
Then, by doing a quick google search, you'll see that dots in env vars are
not supported in most shells and people say to just stay away from them.
With that in mind, I think a great feature to add to the EnvInject plugin
would be to give users the option to replace the dots (and actually any other
which are invalid in env var names) that appear in environment variable names
with an underscore. If you look at this issue that was opened against the
SharedObjects plugin, you'll see that, ...environment variables from tool
names replaces a space, a
dash or a dot to by a underscore.
https://issues.jenkins-ci.org/browse/JENKINS-13673
Please see attached properties files and screenshots.
--
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
Ruben Garat created JENKINS-13925:
-
Summary: 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-13105) allow j/k navigation for search results
[ https://issues.jenkins-ci.org/browse/JENKINS-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163218#comment-163218 ] SCM/JIRA link daemon commented on JENKINS-13105: Code changed in jenkins User: Jesse Farinacci Path: pom.xml src/main/java/org/jenkins/ci/plugins/keyboard_shortcuts/KeyboardShortcutsPageDecorator.java src/main/resources/org/jenkins/ci/plugins/keyboard_shortcuts/KeyboardShortcutsPageDecorator/footer.jelly src/main/resources/org/jenkins/ci/plugins/keyboard_shortcuts/KeyboardShortcutsPageDecorator/footer.properties src/main/resources/org/jenkins/ci/plugins/keyboard_shortcuts/KeyboardShortcutsPageDecorator/header.jelly src/main/webapp/css/keyboard-shortcuts.css src/main/webapp/js/keyboard-shortcuts.js http://jenkins-ci.org/commit/keyboard-shortcuts-plugin/51e77b98c5e2fda9afc7a88ba2a88561e69a1f6b Log: [FIXED JENKINS-13105] allow j/k navigation for search results allow j/k navigation for search results --- Key: JENKINS-13105 URL: https://issues.jenkins-ci.org/browse/JENKINS-13105 Project: Jenkins Issue Type: New Feature Components: keyboard-shortcuts Reporter: jieryn Assignee: jieryn e.g. results page for :: http://ci.jenkins-ci.org/view/Plugins/search/?q=perforce -- 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-13105) allow j/k navigation for search results
[ https://issues.jenkins-ci.org/browse/JENKINS-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13105. Resolution: Fixed allow j/k navigation for search results --- Key: JENKINS-13105 URL: https://issues.jenkins-ci.org/browse/JENKINS-13105 Project: Jenkins Issue Type: New Feature Components: keyboard-shortcuts Reporter: jieryn Assignee: jieryn e.g. results page for :: http://ci.jenkins-ci.org/view/Plugins/search/?q=perforce -- 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
