[JIRA] (JENKINS-62059) JabberIMConnectionProvider.createConnection() swallows Exceptions
Title: Message Title Florian Schmaus started work on JENKINS-62059 Change By: Florian Schmaus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205958.1587971345000.18118.1587978840363%40Atlassian.JIRA.
[JIRA] (JENKINS-62059) JabberIMConnectionProvider.createConnection() swallows Exceptions
Title: Message Title
Florian Schmaus updated an issue
Jenkins / JENKINS-62059
JabberIMConnectionProvider.createConnection() swallows Exceptions
Change By:
Florian Schmaus
Hi [~flow],this is a followup ticket to JENKINS-60193.While I was trying to find out why my connection didn't work, I came across this issue.When an {{XmppStringprepException}} occurs in [JabberIMConnection(JabberPublisherDescriptor desc, AuthenticationHolder authentication)|https://github.com/jenkinsci/jabber-plugin/blob/1.38/src/main/java/hudson/plugins/jabber/im/transport/JabberIMConnection.java#L194], this exception is re-thrown as {{hudson.plugins.im.IMException}}.But in [JabberIMConnectionProvider.createConnection()|https://github.com/jenkinsci/jabber-plugin/blob/1.38/src/main/java/hudson/plugins/jabber/im/transport/JabberIMConnectionProvider.java#L72], only RuntimeExceptions are getting caught.So the log just tells me that the connection failed, but nut *why* it failed:{code :java } h.p.j.i.t.JabberIMConnectionProvider#createConnection: Creating XMPP JabberIMConnection h.p.j.i.t.JabberIMConnectionProvider#createConnection: Connection failed{code} So IMHO here {{Exception}} should get caught here, not only {{RuntimeException}}. RegardsMatthias
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62059) JabberIMConnectionProvider.createConnection() swallows Exceptions
Title: Message Title Florian Schmaus commented on JENKINS-62059 Re: JabberIMConnectionProvider.createConnection() swallows Exceptions https://github.com/jenkinsci/instant-messaging-plugin/pull/40 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205958.1587971345000.18112.1587978780253%40Atlassian.JIRA.
[JIRA] (JENKINS-62059) JabberIMConnectionProvider.createConnection() swallows Exceptions
Title: Message Title Florian Schmaus updated an issue Jenkins / JENKINS-62059 JabberIMConnectionProvider.createConnection() swallows Exceptions Change By: Florian Schmaus Component/s: instant-messaging-plugin Component/s: jabber-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205958.1587971345000.18116.1587978780480%40Atlassian.JIRA.
[JIRA] (JENKINS-62059) JabberIMConnectionProvider.createConnection() swallows Exceptions
Title: Message Title Florian Schmaus commented on JENKINS-62059 Re: JabberIMConnectionProvider.createConnection() swallows Exceptions I had argued that the try/catch should be removed completely and any kind of exception should be handled by higher layers. So the issue is actually that IMConnectionProvider.create() of the jabber-im plugin, silently swallows the exception. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205958.1587971345000.18080.1587973320150%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus commented on JENKINS-60193 Re: NPE in JabberPublisherDescriptor in new install The fix is already in master. You can easily create a snapshot jar of the pluging by running `gradle jpi`. Please report if that fixes the issues for you. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203163.1574067471000.17186.1587733800185%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title Florian Schmaus commented on JENKINS-61029 Re: Swarm client not working anymore with Jenkins 2.220 I've created a PR with a commit that re-adds hudson.UDPBroadcastFragment: https://github.com/jenkinsci/jenkins/pull/4486 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204503.1581328352000.5400.1581340860565%40Atlassian.JIRA.
[JIRA] (JENKINS-61029) Swarm client not working anymore with Jenkins 2.220
Title: Message Title
Florian Schmaus updated an issue
Jenkins / JENKINS-61029
Swarm client not working anymore with Jenkins 2.220
Change By:
Florian Schmaus
Issue most likely casued by JENKINS-60913 h3. SlaveExec:{code:java}java.exe -Xrs -jar "%BASE%\swarm-client-3.17.jar" -mode exclusive -name *** -labels *** -executors 1 -master [http://***] -username *** -password *** -fsroot "%BASE%" -deleteExistingClients -labelsFile "%BASE%\labels"{code}Log:{code:java}Feb 10, 2020 10:25:50 AM hudson.plugins.swarm.SwarmClient discoverFromMasterUrlSEVERE: Failed to fetch slave info from Jenkins, HTTP response code: 500Feb 10, 2020 10:25:50 AM hudson.plugins.swarm.Client runSEVERE: RetryException occurredhudson.plugins.swarm.RetryException: Failed to fetch slave info from Jenkins, HTTP response code: 500 at hudson.plugins.swarm.SwarmClient.discoverFromMasterUrl(SwarmClient.java:248) at hudson.plugins.swarm.Client.run(Client.java:130) at hudson.plugins.swarm.Client.main(Client.java:104)Feb 10, 2020 10:25:50 AM hudson.plugins.swarm.Client runINFO: Retrying in 10 seconds {code}h3. MasterLog:{code:java}2020-02-10 09:50:32.698+ [id=276] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://***/plugin/swarm/slaveInfojava.lang.NoClassDefFoundError: hudson/UDPBroadcastFragmentat hudson.plugins.swarm.PluginImpl.getSwarmSecret(PluginImpl.java:262)at hudson.plugins.swarm.PluginImpl.doSlaveInfo(PluginImpl.java:272)at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)Caused: java.lang.reflect.InvocationTargetExceptionat org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676)at org.kohsuke.stapler.Stapler.service(Stapler.java:238)at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617)[...] {code} Even though The master is unable to load a class: {{ -master
[JIRA] (JENKINS-45607) Potentialy spoofed IQ-packet from ejabberd 17.06 rejected by Smack filter
Title: Message Title Florian Schmaus closed an issue as Fixed Jenkins / JENKINS-45607 Potentialy spoofed IQ-packet from ejabberd 17.06 rejected by Smack filter Change By: Florian Schmaus Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183795.1500382028000.13223.1576701480271%40Atlassian.JIRA.
[JIRA] (JENKINS-45599) Upgrade Smack library to 4.1.9
Title: Message Title Florian Schmaus closed an issue as Fixed Jenkins / JENKINS-45599 Upgrade Smack library to 4.1.9 Change By: Florian Schmaus Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183786.150036859.13224.1576701480283%40Atlassian.JIRA.
[JIRA] (JENKINS-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus closed an issue as Fixed Jenkins / JENKINS-51487 Update Smack to 4.3 Change By: Florian Schmaus Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190847.1527005759000.13220.1576701420618%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus updated JENKINS-60193 Jenkins / JENKINS-60193 NPE in JabberPublisherDescriptor in new install Change By: Florian Schmaus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203163.1574067471000.13219.1576701420607%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus updated JENKINS-60193 Jenkins / JENKINS-60193 NPE in JabberPublisherDescriptor in new install Change By: Florian Schmaus Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203163.1574067471000.13217.1576701420577%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus updated JENKINS-60193 Jenkins / JENKINS-60193 NPE in JabberPublisherDescriptor in new install Change By: Florian Schmaus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203163.1574067471000.13215.1576701300636%40Atlassian.JIRA.
[JIRA] (JENKINS-51173) Replay a scm pipeline job with parameters
Title: Message Title Florian Schmaus stopped work on JENKINS-51173 Change By: Florian Schmaus Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190481.1525684638000.7710.1576418640332%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus updated JENKINS-60193 Jenkins / JENKINS-60193 NPE in JabberPublisherDescriptor in new install Change By: Florian Schmaus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203163.1574067471000.6971.1576227002544%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus started work on JENKINS-60193 Change By: Florian Schmaus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203163.1574067471000.6969.1576226220296%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus updated JENKINS-36826 Jenkins / JENKINS-36826 Support Jenkins Pipeline for Jabber notifications Change By: Florian Schmaus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.18199.1571833923979%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus assigned an issue to Florian Schmaus Jenkins / JENKINS-36826 Support Jenkins Pipeline for Jabber notifications Change By: Florian Schmaus Assignee: Jim Klimov Florian Schmaus Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.10004.1571339524832%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus updated JENKINS-36826 Jenkins / JENKINS-36826 Support Jenkins Pipeline for Jabber notifications Change By: Florian Schmaus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.9970.1571339524145%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications so Florian Schmaus should follow up with the merge of https://github.com/jenkinsci/jabber-plugin/pull/18 That PR has conflicts that you need to resolve first. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.5896.1564691640992%40Atlassian.JIRA.
[JIRA] (JENKINS-16433) Jabber Plugin does not connect: stream:error conflict
Title: Message Title Florian Schmaus closed an issue as Incomplete Jenkins / JENKINS-16433 Jabber Plugin does not connect: stream:error conflict Change By: Florian Schmaus Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.147253.1358805856000.14378.1559077140308%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31979) Enable SASL authentication checkbox missing
Title: Message Title Florian Schmaus closed an issue as Not A Defect Jenkins / JENKINS-31979 Enable SASL authentication checkbox missing Change By: Florian Schmaus Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166938.1449664961000.14370.1559077080578%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29802) jabber plugin disconnects from server with a socket failure
Title: Message Title Florian Schmaus closed an issue as Incomplete No further response, closing. Jenkins / JENKINS-29802 jabber plugin disconnects from server with a socket failure Change By: Florian Schmaus Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164378.1438776433000.14368.1559077080553%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31979) Enable SASL authentication checkbox missing
Title: Message Title Florian Schmaus started work on JENKINS-31979 Change By: Florian Schmaus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166938.1449664961000.14360.1559077020411%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus updated JENKINS-51487 Jenkins / JENKINS-51487 Update Smack to 4.3 Change By: Florian Schmaus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190847.1527005759000.14355.1559076692829%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus updated JENKINS-51487 Jenkins / JENKINS-51487 Update Smack to 4.3 Change By: Florian Schmaus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190847.1527005759000.14353.1559076692810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2, preventing user authentication
Title: Message Title Florian Schmaus updated an issue Jenkins / JENKINS-55683 Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2, preventing user authentication Change By: Florian Schmaus Summary: Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2 , preventing user authentication Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication
Title: Message Title Florian Schmaus updated an issue Jenkins / JENKINS-55683 Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication Change By: Florian Schmaus Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication
Title: Message Title Florian Schmaus updated an issue Jenkins / JENKINS-55683 Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication Change By: Florian Schmaus Environment: Jenkins 2.160 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication
Title: Message Title Florian Schmaus created an issue Jenkins / JENKINS-55683 Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: openid-plugin Created: 2019-01-18 14:22 Priority: Critical Reporter: Florian Schmaus Our users where unable to login using OpenID after upgrading our Jenkins instance from 2.159 to 2.160. Downgrading to 2.159 makes the issue disappear. From a HTTP perspective, Jenkins forwards the user to the OpenID provider URL, which authenticates the user and redirects him back to Jenkins, where a 403 is returned. Which, in turn, causes Jenkins to redirect the user to the OpenID provider, resulting in an endless loop. Unfortunately the logs do not yield any hints. Nevertheless here they are, newest log messages on top: Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.shaded.apache.http.client.protocol.ResponseProcessCookies processCookies Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Starting discovery on URL identifier: http://openid.example.org/user # Here the loop starts again. Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.discovery.Discovery discover Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Received positive auth response. Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.consumer.ConsumerManager verify Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Verifying authentication response... Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.consumer.ConsumerManager verify Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Return URL: https://jenkins.example.org/jenkins/securityRealm/finishLogin matches realm: https://jenkins.example.org/jenkins/securityRealm/finishLogin Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.server.RealmVerifier match Jan 18 12:48:00
[JIRA] (JENKINS-27488) gss.conf file not found
Title: Message Title Florian Schmaus assigned an issue to Unassigned Jenkins / JENKINS-27488 gss.conf file not found Change By: Florian Schmaus Assignee: Florian Schmaus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-16433) Jabber Plugin does not connect: stream:error conflict
Title: Message Title Florian Schmaus assigned an issue to Unassigned Jenkins / JENKINS-16433 Jabber Plugin does not connect: stream:error conflict Change By: Florian Schmaus Assignee: Florian Schmaus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51251) Unable to login to Cisco Jabber Server (bad-request - modify)
Title: Message Title Florian Schmaus reopened an issue Re-opening, since technically, the issue still exists (while a confirmed workaround also exists). Jenkins / JENKINS-51251 Unable to login to Cisco Jabber Server (bad-request - modify) Change By: Florian Schmaus Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-30314) Unable to connect using Jabber plugin (bad-request)
Title: Message Title Florian Schmaus closed an issue as Fixed Jenkins / JENKINS-30314 Unable to connect using Jabber plugin (bad-request) Change By: Florian Schmaus Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus created an issue Jenkins / JENKINS-51487 Update Smack to 4.3 Issue Type: Improvement Assignee: Florian Schmaus Components: jabber-plugin Created: 2018-05-22 16:15 Priority: Minor Reporter: Florian Schmaus Update Smack to 4.3.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51251) Unable to login to Cisco Jabber Server (bad-request - modify)
Title: Message Title Florian Schmaus commented on JENKINS-51251 Re: Unable to login to Cisco Jabber Server (bad-request - modify) SENT: Possibly because the empty resource. As potential workaround try to manually specify a resource by setting the JID to u...@example.org/myresource. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs
Florian Schmaus commented on JENKINS-27507 Support multiple .apk files with different application IDs Hmm I think I got the idea of the "Parametereized Trigger Plugin" and the "Copy Artifact Plugin", What is unclear to me is, how I configure the parameterized trigger plugin to trigger n builds depending on the contents of the directory where my build does store the resulting .apk files. 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] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs
Florian Schmaus commented on JENKINS-27507 Support multiple .apk files with different application IDs I see. Documenting this in the wiki would be really appreciated. Thank you 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] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs
Florian Schmaus
updated JENKINS-27507
Support multiple .apk files with different application IDs
Change By:
Florian Schmaus
(19/Mar/15 1:42 PM)
Description:
Myprojectsbuildsystemproducesmultiple.apkwithdifferentapplicationIDs.Forexamplethereisfoo-main.apk(id:org.foo.main)foo-module-bar.apk(id:org.foo.module.bar)foo-module-baz.apk(id:org.foo.module.baz)currentlythegoogle-play-android-publisher-pluginfailswith
{noformat}
MultipleAPKswerefoundbuttheyhaveinconsistentapplicationIDs:-org.foo.main-org.foo.module.bar-org.foo.module.bazBuildstepUploadAndroidAPKtoGooglePlaymarkedbuildasfailure
{noformat}
Pleaseaddsupportforbuildscreatingmultiple.apkfileswithdifferentapplicationIDs.
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] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs
Florian Schmaus created JENKINS-27507 Support multiple .apk files with different application IDs Issue Type: Improvement Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 19/Mar/15 1:41 PM Description: My project's build system produces multiple .apk with different application IDs. For example there is foo-main.apk (id: org.foo.main) foo-module-bar.apk (id: org.foo.module.bar) foo-module-baz.apk (id: org.foo.module.baz) currently the google-play-android-publisher-plugin fails with Multiple APKs were found but they have inconsistent application IDs: org.foo.main org.foo.module.bar org.foo.module.baz Build step 'Upload Android APK to Google Play' marked build as failure Please add support for builds creating multiple .apk files with different application IDs. Project: Jenkins Priority: Minor Reporter: Florian Schmaus 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] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs
Florian Schmaus updated JENKINS-27507 Support multiple .apk files with different application IDs Change By: Florian Schmaus (19/Mar/15 1:51 PM) Issue Type: Improvement NewFeature Priority: Minor Major 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes HipChat has a similar behavior addressed in JENKINS-25222. Unfortunately it queries the service name for hipchat: https://github.com/jenkinsci/jabber-plugin/commit/cd9eaf5fa28877fc3d2e42339219168ee3f0c0a3#diff-f633f26543fa04f4d2bad3e2c23d6fc3R442 @kutzi I recommend to re-open this issue, changing it's title to "Add support for automated server pings", remove the server specific code added in JENKINS-25222 and add a generic setting for server pings using existing Smack code https://www.igniterealtime.org/builds/smack/docs/latest/javadoc/org/jivesoftware/smackx/ping/PingManager.html I recommend a default ping interval of 5 minutes, but users should be able to enter a longer ping interval (30min, 1h). 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes Create PR to address this issue: https://github.com/jenkinsci/jabber-plugin/pull/13 @Jordan Are you able to create the plugin from the PR and test it? 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus edited a comment on JENKINS-25676 Disconnect from XMPP after a few minutes This is going a bit out of the realm of the jenkins jabber plugin issue tracker. To summarize how the situation appears to me: Either the server or the clients disconnects the XMPP connection. I know Smack and it would tell you why it did so, and this would appear in the Jenkin's log (of the jabber-plugin). I believe Openfire would also log an message if it terminates the connection for some reason. But openfire being a server, logs also many other things, so it's like looking for the needle in the haystack. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes This is going a bit out of the real of the jenkins jabber plugin issue tracker. To summarize how the situation appears to me: Either the server or the clients disconnects the XMPP connection. I know Smack and it would tell you why it did so, and this would appear in the Jenkin's log (of the jabber-plugin). I believe Openfire would also log an message if it terminates the connection for some reason. But openfire being a server, logs also many other things, so it's like looking for the needle in the haystack. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes Those warnings are non-fatal, the faulty packet extension in the presence packet will simply be ignored. @Jordan Did you had a chance to get the server logs? 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes I see that you are using Openfire. Actually what's relevant are not the in/out stanzas logged by the server, but the general log messages that the server produces. For openfire this means, debug, info, warn and error log. They may contain a hint why the connection is closed. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes createVCard method throws an exception the connection gets closed. No, that is not what we are seeing in this issue. The exception is catched and logged by https://github.com/jenkinsci/jabber-plugin/blob/master/src/main/java/hudson/plugins/jabber/im/transport/JabberIMConnection.java#L540 As I tried to explain: There is no evidence that the XMPPException thrown by createVCard is causing the connection termination. In fact the termination as shown in the log happens 10 minutes after the exception is thrown. I guess you are a bit biased towards vcard because of JENKINS-25515. With the information the issue currenctly contains, it's not even clear which side, client or server, sends the closing stream element first, i.e. terminates the stream. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes @Jordan Is it possible to show us the vcard stanza that Smack sends to the server? One could assume that the server sends the 'internal-server-error', and subsequently closes the connection, because of the stanza. Also some logs from the the server side may be helpful to determine the underlying issue. I've no reports that Smack's 4 vcard implementation is broken in this regard, but I'm of course eager to resolve such issues. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus edited a comment on JENKINS-25676 Disconnect from XMPP after a few minutes @Jordan Is it possible to show us the vcard stanza that Smack sends to the server? The interesting part of the logs is actually just before the part you showed us . One could assume that the server sends the 'internal-server-error', and subsequently closes the connection, because of the stanza. Also some logs from the the server side may be helpful to determine the underlying issue. I've no reports that Smack's 4 vcard implementation is broken in this regard, but I'm of course eager to resolve such issues. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes Thanks Jordan for your detailed feedback. Reading the logs and reviewing the issue again, I begin to doubt that this is related to vcard in any way. At least there are no proofs that this is caused by the vcard code. The only hint towards vcard appears in the stacktrace, but this could be pure coincidence. After all it's the server who was closing the connection. The server logs from the relevant time period would sure be helpful. So I don't think that the internal-server-error exception is related to the connection termination at all. What likely happened is that createVCard in JabberIMConnection:537 threw an internal-server-error XMPPException, but this does not mean that the connection will get closed. This only means that the server responded to the vcard IQ request from the client, with an IQ error. The timestamps also strengthen this thesis: the XMPPException is at 5:17:45, but the closing stream elements are send at 5:27:23. @Jordan I think the answer, or at least helpful information what is going on, is found in the server logs (under the assumption that it's the server who is terminating the connection, the timestamps give no clear indication who sends the closing stream element first). @kutzi I recommend reverting the related change and reopening this issue. 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] [jabber-plugin] (JENKINS-25513) jabber-plugin 1.30 fails IPv6 DNS resolve, throws NumberFormatException.
Florian Schmaus commented on JENKINS-25513 jabber-plugin 1.30 fails IPv6 DNS resolve, throws NumberFormatException. I don't think that's it's related to JENKINS-25505. It may appears now because the new Smack version does DNS lookups in case where the old one didn't. It's a 4 year old java bug: https://bugs.openjdk.java.net/browse/JDK-6991580 The workaround is to configure the host and port of the XMPP server in Smack, which will avoid DNS lookups. 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.
