Closed rtyler closed 12 years ago
Vagrant will trap SIGINT
and then resets the SIGINT handler to 'DEFAULT' (busy.rb#L43) which may be clearing Jenkins' handler as well.
Discussed this with @kohsuke on IRC, looks like the JRuby implementation of the Signal
class doesn't properly support the resetting of a handler to 'DEFAULT'.
Working on a patch to the forked Vagrant we're using that calls the Java APIs for doing so instead.
Created https://github.com/jruby/jruby/pull/128 to fix this in JRuby.
After the first Vagrant-baesd job runs inside of Jenkins, the SIGINT/SIGTERM handling gets obliterated, requiring a SIGKILL to stop the server.
This sucks.