Re: Exception when I try to trigger buildflow job from workflow job

2016-01-24 Thread EK
Hi Craig, 

Looks like issue is solved and now can run build flow job from workflow job.
Many thanks for that as now I don't need to convert all my build flow jobs 
to workflow.

question : 
will this be an official fix to the build flow plugin? 

Best Regards




On Sunday, January 24, 2016 at 10:56:59 PM UTC+2, Craig Rodrigues wrote:
>
> Hi,
>
> It looks like you are running under Windows.  I'm not sure if the tests 
> run under Windows.
> Try:
>
> mvn -DskipTests install
>
> --
> Craig
>
> On Jan 24, 2016 4:05 AM, "EK"  wrote:
> >
> > Hi , 
> > I tired to follow your instruction to build the buildflow plugin and and 
> got the following failures : 
> >
> > [ERROR]
> > [ERROR] Please refer to 
> C:\GitTests\build-flow-plugin\target\surefire-reports for the individual 
> test results.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ec95e062-b1af-41c7-a5a4-de04f681492b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Exception when I try to trigger buildflow job from workflow job

2016-01-24 Thread EK
Hi , 
I tired to follow your instruction to build the buildflow plugin and and 
got the following failures : 

Tests run: 45, Failures: 0, Errors: 45, Skipped: 0

[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 12:57 min
[INFO] Finished at: 2016-01-24T13:37:31+02:00
[INFO] Final Memory: 56M/251M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.9:test (default-test) on 
project build-flow-plugin: There are test failures.
[ERROR]
[ERROR] Please refer to 
C:\GitTests\build-flow-plugin\target\surefire-reports for the individual 
test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException



On Saturday, January 23, 2016 at 10:49:12 PM UTC+2, Craig Rodrigues wrote:
>
> Hi,
>
> Thanks for posting your sample scripts.
> I was able to reproduce your problem. 
>
> It looks like the Build Flow plugin needs to change to use the Run class, 
> instead of AbstractBuild
> in order to be compatible with workflow/pipeline plugin.
>
> --
> Craig
>
>
> On Sat, Jan 23, 2016 at 12:22 AM, EK > 
> wrote:
>
>> An example to reproduce :
>>
>> this is my workflow script , it takes param1 (string) from user when 
>> running, and executes buildflowjob : 
>> #
>> println(param1);
>> build job: 'buildflowjob', parameters: [[$class: 'StringParameterValue', 
>> name: 'param1', value:param1]]
>> #
>>
>> this is my buildflowjob script, it takes param1 (string) from user when 
>> running
>> 
>> println(params['param1']));
>> 
>>
>>
>> On Thursday, January 21, 2016 at 3:45:12 PM UTC+2, EK wrote:
>>
>>> Hi , 
>>>
>>>
>>> I am facing the following error , we recently moved to workflow and 
>>> when we try to run\trigger old build flow jobs from workflow jobs we get 
>>> exception:
>>>
>>> Stacktrace of exception is as below , appreciate if anyone can help\advice 
>>> on this and how we can overcome the issue ? 
>>>
>>>
>>> Best Regards
>>>
>>> EK
>>>
>>>
>>> FATAL: Cannot cast object 'MyWorkFlowJobName #3' with class 
>>> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
>>> 'hudson.model.AbstractBuild'org.codehaus.groovy.runtime.typehandling.GroovyCastException
>>>  
>>> <http://stacktrace.jenkins-ci.org/search?query=org.codehaus.groovy.runtime.typehandling.GroovyCastException>:
>>>  Cannot cast object 'MyWorkFlowJobName #3' with class 
>>> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
>>> 'hudson.model.AbstractBuild'
>>> at 
>>> org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
>>>  
>>> <http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType&entity=method>
>>> at 
>>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:599)
>>>  
>>> <http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType&entity=method>
>>> at 
>>> com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall(FlowDSL.groovy:55)
>>>  
>>> <http://stacktrace.jenkins-ci.org/search/?query=com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall&entity=method>
>>> at sun.reflect.GeneratedMethodAccessor1187.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>> at 
>>> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>>> at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>>> at 
>>> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
>>> at groovy.lang.Meta

Re: Exception when I try to trigger buildflow job from workflow job

2016-01-23 Thread EK
An example to reproduce :

this is my workflow script , it takes param1 (string) from user when 
running, and executes buildflowjob : 
#
println(param1);
build job: 'buildflowjob', parameters: [[$class: 'StringParameterValue', 
name: 'param1', value:param1]]
#

this is my buildflowjob script, it takes param1 (string) from user when 
running

println(params['param1']));



On Thursday, January 21, 2016 at 3:45:12 PM UTC+2, EK wrote:

> Hi , 
>
>
> I am facing the following error , we recently moved to workflow and when 
> we try to run\trigger old build flow jobs from workflow jobs we get exception:
>
> Stacktrace of exception is as below , appreciate if anyone can help\advice on 
> this and how we can overcome the issue ? 
>
>
> Best Regards
>
> EK
>
>
> FATAL: Cannot cast object 'MyWorkFlowJobName #3' with class 
> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
> 'hudson.model.AbstractBuild'org.codehaus.groovy.runtime.typehandling.GroovyCastException
>  
> <http://stacktrace.jenkins-ci.org/search?query=org.codehaus.groovy.runtime.typehandling.GroovyCastException>:
>  Cannot cast object 'MyWorkFlowJobName #3' with class 
> 'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
> 'hudson.model.AbstractBuild'
>   at 
> org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType&entity=method>
>   at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:599)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType&entity=method>
>   at 
> com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall(FlowDSL.groovy:55)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall&entity=method>
>   at sun.reflect.GeneratedMethodAccessor1187.invoke(Unknown Source)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>   at java.lang.reflect.Method.invoke(Unknown Source)
>   at 
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>   at 
> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
>   at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
>   at groovy.lang.Closure.call(Closure.java:415)
>   at groovy.lang.Closure.call(Closure.java:428)
>   at 
> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
>   at 
> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
>   at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
> Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>   at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
> Source)
>   at 
> com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods.groovy:26)
>   at sun.reflect.GeneratedMethodAccessor941.invoke(Unknown Source)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>   at java.lang.reflect.Method.invoke(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:51)
>   at 
> org.codehaus.groovy.runtime.metaclass.NewInstanceMetaMethod.invoke(NewInstanceMetaMethod.java:54)
>   at 
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
>   at 
> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
>   at 
> com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:52)
>   at 
> com.cloudbees.plugins.flow.FlowRun$FlyweightTaskRunnerImpl.run(FlowRun.java:219)
>   at hudson.model.Run.execute(Run.java:1738)
>   at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155)
>   at hudson.model.ResourceController.execute(ResourceController.java:98)
>   at hudson.model.Executor.run(Executor.java:410)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/58cd91ef-7810-4c70-9d11-e162c386f5bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Exception when I try to trigger buildflow job from workflow job

2016-01-21 Thread EK


Hi , 


I am facing the following error , we recently moved to workflow and when we 
try to run\trigger old build flow jobs from workflow jobs we get exception:

Stacktrace of exception is as below , appreciate if anyone can help\advice on 
this and how we can overcome the issue ? 


Best Regards

EK


FATAL: Cannot cast object 'MyWorkFlowJobName #3' with class 
'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
'hudson.model.AbstractBuild'org.codehaus.groovy.runtime.typehandling.GroovyCastException
 
<http://stacktrace.jenkins-ci.org/search?query=org.codehaus.groovy.runtime.typehandling.GroovyCastException>:
 Cannot cast object 'MyWorkFlowJobName #3' with class 
'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
'hudson.model.AbstractBuild'
at 
org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
 
<http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType&entity=method>
at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:599)
 
<http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType&entity=method>
at 
com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall(FlowDSL.groovy:55)
 
<http://stacktrace.jenkins-ci.org/search/?query=com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall&entity=method>
at sun.reflect.GeneratedMethodAccessor1187.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at 
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.Closure.call(Closure.java:415)
at groovy.lang.Closure.call(Closure.java:428)
at 
org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
at 
org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
Source)
at 
com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods.groovy:26)
at sun.reflect.GeneratedMethodAccessor941.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:51)
at 
org.codehaus.groovy.runtime.metaclass.NewInstanceMetaMethod.invoke(NewInstanceMetaMethod.java:54)
at 
org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at 
org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at 
com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:52)
at 
com.cloudbees.plugins.flow.FlowRun$FlyweightTaskRunnerImpl.run(FlowRun.java:219)
at hudson.model.Run.execute(Run.java:1738)
at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c8322a8f-c743-4d51-9047-8a472942c5ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: workflow parallel and number of executers

2015-07-26 Thread EK
I think I have managed , but the documentation is diffidently not that 
clear and does not help . 
in my sub workflow script\job - I do only limited stuff surrounded by 
node('master') closer -- this way the executer is released very quickly --> 
 in my case its just load of external groovy script - that has a common 
code and wrapper code for invoking jobs - (this is the reason for moving to 
workflow).

that way the sub workflow script does not consume all available executers 
of the master and they run really in parallel without the need to wait for 
next free executer. 
The only limitation(difference with build flow)  I see now is that the sub 
workflow job is not being running under the same executer( or any other 
executer of the master) --> but this I think I can ignore.


On Sunday, July 26, 2015 at 10:58:06 AM UTC+3, EK wrote:
>
> Hi , 
>   I am trying to move from build flow to workflow , but I am facing many 
> issues in which some i have managed to overcome but now I am facing the 
> following:
> while using build flow when running sub jobs in parallel they all where 
> invoked in same executer on the master , but when I try to do the same in 
> workflow each sub job needs its own executer of the master - and I find 
> myself stuck as some are waiting for next available executer, 
>
> I need help to know how I can invoke sub jobs in parallel while using same 
> executer of the master ?  
>
> Best Regards
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4136b7ab-4561-4df9-8aea-e864ac4c2d81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


workflow parallel and number of executers

2015-07-26 Thread EK
Hi , 
  I am trying to move from build flow to workflow , but I am facing many 
issues in which some i have managed to overcome but now I am facing the 
following:
while using build flow when running sub jobs in parallel they all where 
invoked in same executer on the master , but when I try to do the same in 
workflow each sub job needs its own executer of the master - and I find 
myself stuck as some are waiting for next available executer, 

I need help to know how I can invoke sub jobs in parallel while using same 
executer of the master ?  

Best Regards

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bdbcc4dd-0573-48c8-8979-adbe3ee29ea5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Build Flow Plugin and Folder Plugin issue

2014-05-12 Thread EK
I new it !!! CommonJobs/A  solved the issue , 
I was thinking that this is the only thing I didn't try , thank you very 
much for your quick reply and helpful information.

On Monday, May 12, 2014 12:34:59 AM UTC+3, Daniel Beck wrote:
>
>
> On 11.05.2014, at 22:30, EK > wrote: 
>
> > I tried to pass the path for the job "A" as follow "CommonJobs\A" - 
> (also tried "CommonJobs\\A") but with no luck ! 
>
> CommonJobs/A and /CommonJobs/A should both be valid values. Even 
> ../CommonJobs/A should work. 
>
> IOW, think less like a Windows user ;-) 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Build Flow Plugin and Folder Plugin issue

2014-05-12 Thread EK
I new it !!! CommonJobs/A  solved the issue , 
I was thinking that this is the only thing I didn't try , thank you very 
much for your quick reply and helpful information.

On Sunday, May 11, 2014 11:30:55 PM UTC+3, EK wrote:
>
> Hi ...
>
> I am not able to call a job found in some other folder when running using 
> build flow, 
> my use case is as follow :
> 1. CommonJobs Folder which contain several jobs where "A" is a job among 
> them
> 2. Project1 Folder which contains several jobs and the build flow job.
>
> if the build flow job in Project1 call a jobs found directly under 
> Project1 Folder every thing works fine
> if the build flow job in Project1 Folder call a job found in jenkins 
> default jobs folder every thing works fine 
> if the build flow job in Project1 Folder call a job found in CommonJobs 
> Folder an exception of "JobNotFoundException" is thrown
> this occurs - I think - in the following location:
>
> build-flow-plugin/blob/master/src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy
> at lines 76-78 for some how build flow does not know to look for job in 
> other folders ( beside current and default).
>
> The question is did anyone else try to do this? is there any workaround to 
> make this work ?
> I tried to pass the path for the job "A" as follow "CommonJobs\A" - (also 
> tried "CommonJobs\\A") but with no luck !
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Build Flow Plugin and Folder Plugin issue

2014-05-11 Thread EK
Hi ...

I am not able to call a job found in some other folder when running using 
build flow, 
my use case is as follow :
1. CommonJobs Folder which contain several jobs where "A" is a job among 
them
2. Project1 Folder which contains several jobs and the build flow job.

if the build flow job in Project1 call a jobs found directly under Project1 
Folder every thing works fine
if the build flow job in Project1 Folder call a job found in jenkins 
default jobs folder every thing works fine 
if the build flow job in Project1 Folder call a job found in CommonJobs 
Folder an exception of "JobNotFoundException" is thrown
this occurs - I think - in the following location:
build-flow-plugin/blob/master/src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy
at lines 76-78 for some how build flow does not know to look for job in 
other folders ( beside current and default).

The question is did anyone else try to do this? is there any workaround to 
make this work ?
I tried to pass the path for the job "A" as follow "CommonJobs\A" - (also 
tried "CommonJobs\\A") but with no luck !


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Running a job while slave is offline

2014-03-10 Thread EK
Hi Daniel ...

Can you please give more details ? not sure if I understand how to do what 
you have suggested ? 

Best Regards


On Monday, March 10, 2014 2:35:56 AM UTC+2, Daniel Beck wrote:
>
> Don't run the job on the machine you need to disconnect. Instead, run it 
> somewhere else, and have the build script connect to the actual build/test 
> machine using e.g. SSH and run the commands from there. 
>
> On 08.03.2014, at 13:08, EK > wrote: 
>
> > Hi ... 
> > 
> > I need to run a job which might cause slave to disconnect from Jenkins 
> server for a while- currently if slave is disconnected job is immediately 
> marked as failed or aborted, is there a way to do this, I was thinking 
> about something like the follow: 
> > 1. send job to slave 
> > 2. go offline 
> > 3. run job 
> > 4. go online 
> > 5. report results ... 
> > 
> > Best Regards 
> > EK 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Jenkins Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to jenkinsci-use...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Running a job while slave is offline

2014-03-10 Thread EK
The case is as follow , I don't control when the job I am running will 
cause a disconnection between slave and jenkins server - it could happen at 
any time.
anyway  I will try your suggestion below and see if it will work for me.
Thanks for your reply and best regards


On Monday, March 10, 2014 2:31:40 AM UTC+2, Christian Willman wrote:
>
> Hi EK,
>
> What's the purpose of this exercise? It's very strange indeed.
>
> I guess you could add two System Groovy scripts to the particular job. The 
> first script is the first builder in the job's builders list, and it grabs 
> a reference to the slave via 
> jenkins.model.Jenkins.getInstance()#getComputer(...) and mark it as offline 
> with setTemporarilyOffline(...). The next builder will perform whatever 
> tasks you want, and a final System Groovy script will mark the slave as 
> online.
>
> If you can more thoroughly describe your goals then we can likely suggest 
> a better means.
>
> Cheers,
> Christian
>
> On Saturday, March 8, 2014 7:08:07 AM UTC-5, EK wrote:
>>
>> Hi ...
>>
>> I need to run a job which might cause slave to disconnect from Jenkins 
>> server for a while- currently if slave is disconnected job is immediately 
>> marked as failed or aborted, is there a way to do this, I was thinking 
>> about something like the follow:
>> 1. send job to slave
>> 2. go offline
>> 3. run job
>> 4. go online
>> 5. report results ...
>>
>> Best Regards
>> EK
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Running a job while slave is offline

2014-03-08 Thread EK
Hi ...

I need to run a job which might cause slave to disconnect from Jenkins 
server for a while- currently if slave is disconnected job is immediately 
marked as failed or aborted, is there a way to do this, I was thinking 
about something like the follow:
1. send job to slave
2. go offline
3. run job
4. go online
5. report results ...

Best Regards
EK

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How to run a job which will require the slave to go offilne for while ?

2013-11-13 Thread EK
Hi All ...

My Scenario is as follows , I need to trigger a script( via jenkins job) , 
this script might cause disconnection between jenkins slave and jenkisn 
server which will cause the job to be marked as failed \aborted  ?
is there any way that I can go around this issue ? 
any special plug in that will allow me to continue running jobs even if 
slave goes offline while server retry to reconnect before it marks job 
stats as aborted or failed ?


Best Regards
EK

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.