KB,
If it is possible to turn the JMS plugin back on it seems to be the JMS Messaging plugin with pipelines. I removed the multibranch ci-pipeline job. I believe this is why we haven't seen an issue until now since we just turned this on yesterday.
Is there any chance we can turn that plugin on and just use it for freestyle jobs?
Thanks
On Wed, Jun 14, 2017 at 1:55 PM, Ari LiVigni alivigni@redhat.com wrote:
fyi Scott is looking into issues on his test instance to see if he can identify the issue while we wait.
On Wed, Jun 14, 2017 at 1:46 PM, Ari LiVigni alivigni@redhat.com wrote:
On Wed, Jun 14, 2017 at 1:43 PM, Karanbir Singh kbsingh@centos.org wrote:
On 14/06/17 18:35, Ari LiVigni wrote:
I've disabled the JMS Plugin for now, that seems to have had a huge impact on the system stability. Am going to leave that off till wecan
workout what the underlaying issue here is. Regards,Scott wrote that plugin and can look at what is happening. We need
that
for our pipeline triggering it has been working fine for a while so it would be good to understand what the root cause issue is before just disabling it.
the guys are looking at a new bringup, lets get that up with the JMS stuff and diagnose that before moving the rest of the projects over/. Would that work ?
Its important we keep jenkins up for now,
I am fine with that but what shows that plugin is the culprit? Is there some logs or something that can be sent over to Scott?
Thanks,
-- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
-- -== @ri ==-
-- -== @ri ==-