I am using hudson which will run scheduled builds from time to time.
Problem is that i configured a shell script which will be excuted to perform the deployment and also restarting of domain.
As hudson is on the same application server as the actual application.
My hudson will stop and also stop the shell script after the asadmin stop-domain command so it doesn't proceed to start back the domain.
What can i do to resolve this issue?
Hi dfdfd! (funny handle)
We have a customer that uses Nolio (http://www.noliosoft.com) in conjunction with Hudson, so when the build is finished it triggers a Nolio Process. This process can also live across reboots, so it seems that it will be a good match for you as well. Let me know if you need more information.
Best, Daniel
Daniel is right. Every process that Hudson starts will be destroyed when Hudson shuts down. So you need a way to have a process outside of Hudson pick up that signal. You can do that with a separate process that checks a directory periodically and performs an action according to files that will be created in that directory. The safest way is to code the action in the filename. However, a message to any non-Hudson process will do as well.