[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-11-18 Thread st...@diligent.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Teti commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 I can confirm that the latest master (83a8c0a) fixed this issue for me.  
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.2693.1574097360384%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-11-12 Thread mjdean1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Dean commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 KaiHsiang Chang has this fix been released? This is a blocker for my team currently.  
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.12551.1573586280320%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-10-16 Thread cash9...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 KaiHsiang Chang commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 Already merged the patch, but still need Gavin Mogan to test.   
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.9385.1571290620388%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-10-16 Thread raihaan.shouh...@autodesk.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raihaan Shouhell commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 Tbh I cant consistently reproduce this. Occasionally this fails due to attempting to serialize a semaphore.  
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.9375.1571285580339%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-10-16 Thread jenk...@gavinmogan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 Oh totally missed the comment saying its potentially fixed <_< I'll see if we can reproduce the original case on our jenkins  
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.9329.1571280660342%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-10-16 Thread jenk...@gavinmogan.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 Owen Mehegan or others do you have the actual reproduction steps? the tests arn't failing at any version.  
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.9320.1571280360284%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-10-06 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace: {code:java} an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see  [ https://jenkins.io/redirect/class-filter/ ]  at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration#hostLocks for class org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.though

[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-10-04 Thread raihaan.shouh...@autodesk.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raihaan Shouhell commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 Owen Mehegan could you try the build that comes out of     https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/59  
 

  
 
 
 
 

 
 
 

 
 
 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.198414.155366818.946.1570185060487%40Atlassian.JIRA.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-29 Thread yixi...@medallia.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yixiao Lin commented on  JENKINS-56770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
 We experience the same issue. Would be great if this is 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace:an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see [https://jenkins.io/redirect/class-filter/] at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration#hostLocks for class org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.co

[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 
 
Attachment: 
 exception.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace:{{  an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see [https://jenkins.io/redirect/class-filter/] at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration#hostLocks for class org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstrea

[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace: {{ an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see [https://jenkins.io/redirect/class-filter/] at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration#hostLocks for class org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstrea

[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace:{{an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see  [  https://jenkins.io/redirect/class-filter/ ]  at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration#hostLocks for class org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xst

[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace: {noformat}  {{ an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration#hostLocks for class org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtwo

[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes

2019-03-26 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56770  
 
 
  Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 KaiHsiang Chang  
 
 
Components: 
 parameterized-remote-trigger-plugin  
 
 
Created: 
 2019-03-27 06:29  
 
 
Environment: 
 Parameterized Remote Trigger v3.0.7, Jenkins 2.150.2  
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Owen Mehegan  
 

  
 
 
 
 

 
 When calling the org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep using Jenkins 2.150.2, we get the following stack trace: 

 
an exception which occurred:an exception which occurred: in field org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution.remoteBuildConfig in object org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep$Execution@14b8f445 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@3350481e in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@2e15e1a9Caused: java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.Semaphore for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStre