On Wednesday, September 13, 2017 at 11:20:55 AM UTC+2, harvey wrote:
>
>
>
> On Tuesday, September 12, 2017 at 7:21:55 PM UTC+2, [email protected] 
> wrote:
>>
>> Take care that you are actually chaining batch command. What is chaining 
>> batch, someone somewhere though it would be nice to make this super weird 
>> feature for batch script only (yeah a lot of sarcasm here, the first time 
>> you see this beahavior and realize wtf someone wanted to do this is beyond 
>> total common sense), where you call a batch from another batch script, the 
>> remaining in between one can be skipped entirely. Here's the documentation 
>> from https://jpsoft.com/help/call.htm which give a better explanation of 
>> this eye bleeding nightmare:
>>
>> WARNING! If you execute a batch file from inside another batch file 
>> without using CALL, the original batch file is terminated before the other 
>> one starts. This method of invoking a batch file from another is usually 
>> referred to as chaining. Note that if the batch file A.BTM uses CALL B, 
>> and B.BTM chains to the batch file C.BTM, on exit from C.BTM (without 
>> executing a CANCEL <https://jpsoft.com/help/cancel.htm> command) 
>> processing of batch file A.BTM is resumed as if it had used CALL C.
>>
>
> But I am using CALL to run the other batch file. The problem is when I run 
> the build, it is completed successfully. But the server is still not 
> started. The commands works great in CMD and also I tried creating a batch 
> file and even it works fine. And again I tried calling the batch file I 
> created into Jenkins, yet there was no success. The problem still remained 
> and the server was still not started.
>
>>
>>
>> I suspect that the Jenkins shell execute the script you gave it as it is 
>> a call itself maybe, maybe the Jenkins people can shed some light on this.
>>
>
>
> Regards,
> Harvey
>

By using the following link: 
https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller, I edited the 
command as follows:

cd c:\glassfish3\bin\
asadmin start-domain
$BUILD_ID=dontKillMe 

But it didn't solve my problem though. I am sure that this is not the way. 
I am new user to Jenkins, I have no idea about using environment variables. 
Any help would be appreciated, I am blocked at this stage, would be 
grateful if anyone could guide me in this regard.

Regards,
Harvey

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a3b7ef0b-1fbb-4bbc-b8a6-1cda2df84f1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to