[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs

2019-11-19 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand updated  JENKINS-37557  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37557  
 
 
  Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Francois Ferrand  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs

2019-11-19 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand updated  JENKINS-37557  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Solution available in repo 1.10 release, by explicitely specifying the 'extraEnvVars' argument: 

 

sshAgent(['gerrit-ssh-credentials-id']) {
  checkout([$class: 'RepoScm', manifestRepositoryUrl: 'ssh://server/project',
extraEnvVars: getContext(hudson.EnvVars)])
}
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37557  
 
 
  Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Francois Ferrand  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Assignee: 
 Francois Ferrand  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 https://github.com/jenkinsci/repo-plugin/releases/tag/repo-1.11.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-37557) Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs

2019-09-16 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand commented on  JENKINS-37557  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permission denied when using repo plugin with ssh-agent plugin in pipeline jobs   
 

  
 
 
 
 

 
 I created a pull-request which allows to overcome this, by passing explicitely `getContext(hudson.EnvVars)` when creating the RepoScm object. https://github.com/jenkinsci/repo-plugin/pull/54 May not be a full solution, but works fine as a stop-gap pending, until support for (multiple) credentials is baked into the plugin.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-56682) Unable to use @Field annotations

2019-03-22 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56682  
 
 
  Unable to use @Field annotations   
 

  
 
 
 
 

 
Change By: 
 Francois Ferrand  
 
 
Environment: 
 Jenkins: 2.168Pipeline: Groovy 2.64 script-security: 1.54  
 

  
 
 
 
 

 
 
 

 
 
 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-56682) Unable to use @Field annotations

2019-03-22 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56682  
 
 
  Unable to use @Field annotations   
 

  
 
 
 
 

 
Change By: 
 Francois Ferrand  
 

  
 
 
 
 

 
 Since the workflow-cps was upgraded to 2.64, @Field annotations are not working anymore.The following pipeline works fine in 2.63:{code:java}import groovy.transform.Field@Field final SOMETHING='bar'@Field final MY_CONSTANT="foo $SOMETHING"node() {  do_stuff()}def do_stuff() {  sh "echo $MY_CONSTANT"}{code}With workflow-cps 2.64, this gives the following exception: {noformat}roovy.lang.MissingPropertyException: No such property: SOMETHING for class: groovy.lang.Binding   at groovy.lang.Binding.getVariable(Binding.java:58)   at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264)   at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288)   at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292)   at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source)   at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:230)   at WorkflowScript.(WorkflowScript:3) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)   at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442)   at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:434)   Caused: groovy.lang.GroovyRuntimeException: Failed to create Script instance for class: class WorkflowScript. Reason   at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:466)   at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.lambda$doParse$0(CpsGroovyShell.java:135)   at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136)   at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:132)   at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)   at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560)   at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521)   at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320)   at hudson.model.ResourceController.execute(ResourceController.java:97)   at hudson.model.Executor.run(Executor.java:429)   Finished: FAILURE{noformat}  
 

  
   

[JIRA] (JENKINS-56682) Unable to use @Field annotations

2019-03-22 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56682  
 
 
  Unable to use @Field annotations   
 

  
 
 
 
 

 
Change By: 
 Francois Ferrand  
 

  
 
 
 
 

 
 Since the workflow-cps was upgraded to 2.64, @Field annotations are not working anymore.The following pipeline works fine in 2.63:{code:java}import groovy.transform.Field@Field final SOMETHING='bar'@Field final MY_CONSTANT="foo $SOMETHING"node() {  do_stuff()}def do_stuff() {  sh "echo $MY_CONSTANT"}{code}With workflow-cps 2.64, this gives the following exception: {noformat} roovy Groovy .lang.MissingPropertyException: No such property: SOMETHING for class: groovy.lang.Binding   at groovy.lang.Binding.getVariable(Binding.java:58)   at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264)   at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288)   at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292)   at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source)   at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194)   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:230)   at WorkflowScript.(WorkflowScript:3) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)   at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442)   at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:434)Caused: groovy.lang.GroovyRuntimeException: Failed to create Script instance for class: class WorkflowScript. Reason   at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:466)   at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.lambda$doParse$0(CpsGroovyShell.java:135)   at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136)   at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:132)   at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)   at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560)   at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521)   at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320)   at hudson.model.ResourceController.execute(ResourceController.java:97)   at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}  
 

  

[JIRA] (JENKINS-56682) Unable to use @Field annotations

2019-03-22 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56682  
 
 
  Unable to use @Field annotations   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2019-03-22 13:25  
 
 
Environment: 
 Jenkins: 2.168  Pipeline: Groovy 2.64  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Francois Ferrand  
 

  
 
 
 
 

 
 Since the workflow-cps was upgraded to 2.64, @Field annotations are not working anymore. The following pipeline works fine in 2.63: 

 

import groovy.transform.Field
@Field final SOMETHING='bar'
@Field final MY_CONSTANT="foo $SOMETHING"
node() {
  do_stuff()
}
def do_stuff() {
  sh "echo $MY_CONSTANT"
}
 

 With workflow-cps 2.64, this gives the following exception:   

 
roovy.lang.MissingPropertyException: No such property: SOMETHING for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:58) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264) at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at 

[JIRA] (JENKINS-32766) groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError

2017-01-05 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand commented on  JENKINS-32766  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError   
 

  
 
 
 
 

 
 Delegation strategy is actually set correctly, but it seems that it is ignored when trying to resolve the function call: probably an issue in the sandbox interceptor or CpsScript/DSL invokeMethod.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-32766) groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError

2017-01-05 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand edited a comment on  JENKINS-32766  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError   
 

  
 
 
 
 

 
 I managed to have this working: need to add 'delegate' before each tag:{code:java}xml.records() { delegate.car(name:'HSV Maloo', make:'Holden', year:2006) {delegate.country('Australia')delegate.record(type:'speed', 'Production Pickup Truck with speed of 271kph')}delegate.car(name:'Royale', make:'Bugatti', year:1931) {delegate.country('France')delegate.record(type:'price', 'Most Valuable Car at $15 million')}}{code}Maybe this is a problem with the closure delegation strategy, set to Closure.OWNER_ONLY  or a custom (e.g. Closure.TO_SELF) strategy which does not try the delegate  ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-32766) groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError

2017-01-05 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32766  
 
 
  groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError   
 

  
 
 
 
 

 
Change By: 
 Francois Ferrand  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-32766) groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError

2017-01-05 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand commented on  JENKINS-32766  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError   
 

  
 
 
 
 

 
 I managed to have this working: need to add 'delegate' before each tag: 

 

xml.records() { 
delegate.car(name:'HSV Maloo', make:'Holden', year:2006) {
delegate.country('Australia')
delegate.record(type:'speed', 'Production Pickup Truck with speed of 271kph')
}
delegate.car(name:'Royale', make:'Bugatti', year:1931) {
delegate.country('France')
delegate.record(type:'price', 'Most Valuable Car at $15 million')
}
}
 

 Maybe this is a problem with the closure delegation strategy, set to Closure.OWNER_ONLY ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-34290) FlakyTestResult doesn't catch NullPointerException

2016-11-03 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand commented on  JENKINS-34290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FlakyTestResult doesn't catch NullPointerException   
 

  
 
 
 
 

 
 any plan for a release with this fix? Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-36987) GerritMissedEventsPlaybackManager does not correctly handle multiple gerrit servers

2016-07-27 Thread thet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francois Ferrand created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36987  
 
 
  GerritMissedEventsPlaybackManager does not correctly handle multiple gerrit servers   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 gerrit-trigger-plugin  
 
 
Created: 
 2016/Jul/27 8:39 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Francois Ferrand  
 

  
 
 
 
 

 
 There is a single instance of GerritMissedEventsPlaybackManager, which stores a single status for all Gerrit servers. This causes a few issues: 
 
A single timestamp is stored for all servers, instead of storing (and re-loading) each server's timestamp 
If one server supports event-log and not the other, the isSupported flag is set to false, preventing use of the feature for all servers 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

 

[JIRA] [repo-plugin] (JENKINS-26836) Repo support for Workflow

2016-01-25 Thread thet...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francois Ferrand resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26836 
 
 
 
  Repo support for Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francois Ferrand 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [repo-plugin] (JENKINS-26836) Repo support for Workflow

2015-12-23 Thread thet...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francois Ferrand started work on  JENKINS-26836 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Francois Ferrand 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [repo-plugin] (JENKINS-26836) Repo support for Workflow

2015-12-23 Thread thet...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francois Ferrand commented on  JENKINS-26836 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Repo support for Workflow  
 
 
 
 
 
 
 
 
 
 
Fixed in this pull request: https://github.com/jenkinsci/repo-plugin/pull/28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.