[JIRA] [multi-branch-project-plugin] (JENKINS-32388) Multi-branch plugin: Temporal error when syncing branches during build

2016-02-18 Thread a...@varju.ca (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Varju commented on  JENKINS-32388 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multi-branch plugin: Temporal error when syncing branches during build  
 
 
 
 
 
 
 
 
 
 
I'm seeing this too. Another thing that's biting me, possibly related to this, is that frequently I'll end up with a second build of the same commit being kicked off, presumably because Jenkins doesn't know it's already building that commit. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-37527) IllegalArgumentException: array element type mismatch from GroovyCallSiteSelector.parametersForVarargs calling String.join with a List

2017-03-29 Thread a...@varju.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Varju commented on  JENKINS-37527  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IllegalArgumentException: array element type mismatch from GroovyCallSiteSelector.parametersForVarargs calling String.join with a List   
 

  
 
 
 
 

 
 Seeing the same thing here when calling a constructor that has overloads where one variant uses varargs: 

 

String paramName = "whatever"
List parameters = [ new BooleanParameterValue( paramName, true ) ]
Collection additionalSafeParameters = [ paramName ]
new ParametersAction( parameters, additionalSafeParameters )
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-50470) Cannot evaluate ArrayList.name inside Groovy Sandbox

2018-05-07 Thread a...@varju.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Varju commented on  JENKINS-50470  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot evaluate ArrayList.name inside Groovy Sandbox   
 

  
 
 
 
 

 
 I'm seeing very similar behaviour with 1.44.  In my freestyle job I've got this Groovy: 

 
def someList = [1, 2, 3]
println someList.size
 

 When the sandbox is enabled, this ends up throwing: 

 
RejectedAccessException: No such field found: field java.lang.Integer size
 

 Changing the list to contain strings changes the error to: 

 
RejectedAccessException: No such field found: field java.lang.String size
 

  
 

  
 
 
 
 

 
 
 

 
 
 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, 

[JIRA] (JENKINS-50470) Cannot evaluate ArrayList.name inside Groovy Sandbox

2018-05-23 Thread a...@varju.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Varju commented on  JENKINS-50470  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot evaluate ArrayList.name inside Groovy Sandbox   
 

  
 
 
 
 

 
 Unfortunately, no. In the case above, I had to refactor my code to use `someList.size()` Since commenting previously, I've encountered at least one other example of a similar failure: 

 
def tuple = new Tuple2( 'a', 'b' )
println tuple.first
 

 Which results in: 

 
RejectedAccessException: No such field found: field java.lang.String first
 

 And again, changing tuple.first to tuple.getFirst() works around the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-50470) Cannot evaluate ArrayList.name inside Groovy Sandbox

2018-05-23 Thread a...@varju.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Varju edited a comment on  JENKINS-50470  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot evaluate ArrayList.name inside Groovy Sandbox   
 

  
 
 
 
 

 
 Unfortunately, no.  In the case above, I had to refactor my code to use  `  {{ someList.size() ` }} Since commenting previously, I've encountered at least one other example of a similar failure:{noformat}def tuple = new Tuple2( 'a', 'b' )println tuple.first{noformat}  Which results in:{noformat}RejectedAccessException: No such field found: field java.lang.String first{noformat}  And again, changing {{tuple.first}} to {{tuple.getFirst()}} works around the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines

2019-12-04 Thread a...@varju.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Varju commented on  JENKINS-34256  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Preparing Jenkins For Shutdown Hangs Running Pipelines   
 

  
 
 
 
 

 
 In the modern world of transient agents (e.g. Kubernetes pods) that won't exist after restart, this approach of pausing the pipeline is painful.  It would sure be nice if there was a way to allow current jobs to finish while not allowing queued jobs to be started.  
 

  
 
 
 
 

 
 
 

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