Have you looked at using the Start command? As I understand it, it starts a 
process in a different context. In this way, when the Jenkins job ends, it 
doesnt shut down the service since its in a different context.

On Friday, September 15, 2017 at 4:01:58 AM UTC-4, harvey wrote:
>
> Currently I am just trying to create a single build to Start the glassfish 
> server. For the same I used a freestyle project and by selecting "Run a 
> batch windows command line" in building steps I wrote the following 
> commands:
>
> cd c:\glassfish3\bin
> call asadmin start-domain
>
> Then I saved the build and executed it. The build completes with status 
> success, but the glassfish server remain unstarted.
>
> Other than these steps I haven't done any other steps. I did not set an 
> ERROR LEVEL. 
>
> Is there something I am missing ?
>
> 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/bf19be64-6f59-4c90-a152-91c97d240985%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to