[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak edited a comment on  JENKINS-52005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
  {code:java}node {stage("successful"){echo "successful stage"}stage("unstable"){catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'){sh "gooo version"}}stage("continue working"){echo "continue working"}}{code}  I also have this is issue.Jenkins v2.164.3 (Basic Steps 2.18)  already installer doesn't work if I update Basic Steps but when I was testing on new spiup Jenkins with the same version 2.164.3 it is work  !Screen Shot 2019-06-27 at 4.02.19 PM.png|thumbnail!  !Screen Shot 2019-06-27 at 4.02.56 PM.png|thumbnail!
 

  
 
 
 
 

 
 
 

 
 
 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.191506.1529326312000.10677.1561640820499%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52005  
 
 
  catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 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.191506.1529326312000.10679.1561640820524%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52005  
 
 
  catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
Attachment: 
 Screen Shot 2019-06-27 at 4.02.19 PM.png  
 
 
Attachment: 
 Screen Shot 2019-06-27 at 4.02.56 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 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.191506.1529326312000.10669.1561640760335%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak commented on  JENKINS-52005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
 

 

node {
stage("successful"){
echo "successful stage"
}
stage("unstable"){
catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'){
sh "gooo version"
}
}
stage("continue working"){
echo "continue working"
}
}
 

 I also have this is issue. Jenkins v2.164.3 already installer doesn't work if I update Basic Steps but when I was testing on new spiup Jenkins with the same version 2.164.3 it is work  
 

  
 
 
 
 

 
 
 

 
 
 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.191506.1529326312000.10671.1561640760361%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55151) GitHub Branch Source Plugin: Failed branch indexing

2018-12-12 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55151  
 
 
  GitHub Branch Source Plugin: Failed branch indexing
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 

  
 
 
 
 

 
 GitHub Branch Source had already been working but now We can't indexing repo:{code:java}[Wed Dec 12 13:23:19 UTC 2018] Starting branch indexing... 13:23:19 Connecting to https://api.github.com using twcsysadmins/** (twcsysadmins github api token)ERROR: [Wed Dec 12 13:23:19 UTC 2018] Could not update folder level actions from source 12ca09af-4dfe-4959-8266-0b82428ee176 java.lang.ArrayIndexOutOfBoundsException: 1 at org.kohsuke.github.GitHub.getRepository(GitHub.java:474) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieveActions(GitHubSCMSource.java:1667) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:765) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:590) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Wed Dec 12 13:23:19 UTC 2018] Finished branch indexing. Indexing took 0 ms FATAL: Failed to recompute children of wxu-armada-cluster-secret java.lang.ArrayIndexOutOfBoundsException: 1 at org.kohsuke.github.GitHub.getRepository(GitHub.java:474) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieveActions(GitHubSCMSource.java:1667) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:765) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:590) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE{code}GitHub Branch Source have any limits ?Because we have quite big organization.  
 

  
 
 
 
 

 
 
 

 
 
 

[JIRA] (JENKINS-46492) Multibranch Pipelines fail first scan with Bitbucket

2018-12-12 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46492  
 
 
  Multibranch Pipelines fail first scan with Bitbucket   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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-46492) Multibranch Pipelines fail first scan with Bitbucket

2018-12-12 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46492  
 
 
  Multibranch Pipelines fail first scan with Bitbucket   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
Priority: 
 Blocker Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-46492) Multibranch Pipelines fail first scan with Bitbucket

2018-12-12 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46492  
 
 
  Multibranch Pipelines fail first scan with Bitbucket   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 

  
 
 
 
 

 
 I can't finish the creation of a new Multibranch Pipeline with BitBucket source because it fails listing available projects in the account. The select box that shows the projects is empty and the only error I can see in the logs is the following:{code:java}Started [Mon Aug 28 10:50:33 CEST 2017] Starting branch indexing...ERROR: [Mon Aug 28 10:50:33 CEST 2017] Could not update folder level actions from source 08a4d320-a290-4de7-999a-736b4f5e3906 java.io.FileNotFoundException: URL: }}{{[https://api.bitbucket.org/2.0/repositories//]}}{{ at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:595) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:235) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveActions(BitbucketSCMSource.java:963) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:419)[Mon Aug 28 10:50:33 CEST 2017] Finished branch indexing. Indexing took 0.15 sec FATAL: Failed to recompute children of test java.io.FileNotFoundException: URL: }}{{[https://api.bitbucket.org/2.0/repositories//]}}{{ at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:595) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:235) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveActions(BitbucketSCMSource.java:963) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:419)   Finished: FAILURE{code}There is no {{//}} in the end of the Bitbucket API URL and that's why it fails.  
 

  
 
 

[JIRA] (JENKINS-46492) Multibranch Pipelines fail first scan with Bitbucket

2018-12-12 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46492  
 
 
  Multibranch Pipelines fail first scan with Bitbucket   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 

  
 
 
 
 

 
 I can't finish the creation of a new Multibranch Pipeline with BitBucket source because it fails listing available projects in the account. The select box that shows the projects is empty and the only error I can see in the logs is the following:  { {noformat code:java } } Started [Mon Aug 28 10:50:33 CEST 2017] Starting branch indexing... ERROR: [Mon Aug 28 10:50:33 CEST 2017] Could not update folder level actions from source 08a4d320-a290-4de7-999a-736b4f5e3906 java.io.FileNotFoundException: URL: }}{{[https://api.bitbucket.org/2.0/repositories//]}}{{ at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:595) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:235) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveActions(BitbucketSCMSource.java:963) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:419) [Mon Aug 28 10:50:33 CEST 2017] Finished branch indexing. Indexing took 0.15 sec FATAL: Failed to recompute children of test java.io.FileNotFoundException: URL: }}{{[https://api.bitbucket.org/2.0/repositories//]}}{{ at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:595) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:235) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveActions(BitbucketSCMSource.java:963) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:419) Finished: FAILURE{ {noformat code } }   There is no {{//}} in the end of the Bitbucket API URL and that's why it fails.  
 

  
 

[JIRA] (JENKINS-55151) GitHub Branch Source Plugin: Failed branch indexing

2018-12-12 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55151  
 
 
  GitHub Branch Source Plugin: Failed branch indexing
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2018-12-12 14:00  
 
 
Environment: 
 Jenkins ver. 2.121.3  GitHub Branch Source 2.4.0  
 
 
Labels: 
 jenkins github github-branch-source-plugin  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Alexandr Semak  
 

  
 
 
 
 

 
 GitHub Branch Source had already been working but now We can't indexing repo: 

 

[Wed Dec 12 13:23:19 UTC 2018] Starting branch indexing... 13:23:19 Connecting to https://api.github.com using twcsysadmins/** (twcsysadmins github api token) ERROR: [Wed Dec 12 13:23:19 UTC 2018] Could not update folder level actions from source 12ca09af-4dfe-4959-8266-0b82428ee176 java.lang.ArrayIndexOutOfBoundsException: 1 at org.kohsuke.github.GitHub.getRepository(GitHub.java:474) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieveActions(GitHubSCMSource.java:1667) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:765) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:590) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024) 

[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline

2018-10-29 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54322  
 
 
  Add ability SKIP stage in script pipeline   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
Labels: 
 Script  jekins pipleine  jenkins pipeline  
 

  
 
 
 
 

 
 
 

 
 
 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-54322) Add ability SKIP stage in script pipeline

2018-10-29 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54322  
 
 
  Add ability SKIP stage in script pipeline   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 

  
 
 
 
 

 
 I try to improve visualization for pipeline.I want skip stage and mark skip stage as skip.But using Skripted Pipeline i must approve signature. {code:java}staticMethod org.jenkinsci.plugins.pipeline.modeldefinition.Utils markStageSkippedForConditional java.lang.String{code} Using it: {code:java}import org.jenkinsci.plugins.pipeline.modeldefinition.Utilsmap_dev = ["dev", "qa", "stage" ,"perf"]prodPromoter = nullmap_dev.each { stage("${it}") {  try{   prodPromoter = input(message: "Deploy ${it}")  } catch(e){   Utils.markStageSkippedForConditional("${it}")  } }}{code}  I now that i can using Declarative Pipeline like this: {code:java}when { _expression_ {   try {devPromoter = input(message: "Deploy")   } catch(e) { return false   }  } } steps { }{code} BUT,  can  Could  you  please  just add Utils.markStageSkippedForConditional to @whitelist ?Because Scripted pipleine more readable and flexible for me...  Thank you for advance!  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline

2018-10-29 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54322  
 
 
  Add ability SKIP stage in script pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-10-29 19:46  
 
 
Environment: 
 Jenkins ver. 2.138.2  
 
 
Labels: 
 jekins Script pipleine  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Alexandr Semak  
 

  
 
 
 
 

 
 I try to improve visualization for pipeline. I want skip stage and mark skip stage as skip. But using Skripted Pipeline i must approve signature.   

 

staticMethod org.jenkinsci.plugins.pipeline.modeldefinition.Utils markStageSkippedForConditional java.lang.String 

   Using it:  

 

import org.jenkinsci.plugins.pipeline.modeldefinition.Utils
map_dev = ["dev", "qa", "stage" ,"perf"]

prodPromoter = null

map_dev.each {
 stage("${it}") {
  try{
   prodPromoter = input(message: "Deploy ${it}")
  } catch(e){
   Utils.markStageSkippedForConditional("${it}")
  }
 }
}
 

    I now that i can using Declarative Pipeline like this: