Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
Severity 2 - Major
-
Description
Issue Summary
Currently the startup script for the MacOS Runner is not able to intercept the ctrl+c signal to terminate the runner. Hence the runner cannot be stopped from the terminal.
This is reproducible on the MacOS Runner : Yes
Steps to Reproduce
- Start MacOS runner using the startup script.
- Press ctrl+c to stop the runner
Expected Results
Runner should stop.
Actual Results
Runner does not stop.
Workaround
Kill the runner using the Activity List
OR
Use the following to start the runner from the terminal and use "ctrl+c" to stop it:
java \ -jar \ -Dbitbucket.pipelines.runner.account.uuid=$accountUuid \ -Dbitbucket.pipelines.runner.repository.uuid=$repositoryUuid \ -Dbitbucket.pipelines.runner.uuid=$runnerUuid \ -Dbitbucket.pipelines.runner.oauth.client.id=$OAuthClientId \ -Dbitbucket.pipelines.runner.oauth.client.secret=$OAuthClientSecret \ -Dbitbucket.pipelines.runner.directory.working=$workingDirectory \ -Dbitbucket.pipelines.runner.environment=PRODUCTION \ -Dbitbucket.pipelines.runner.runtime=macos-bash \ -Dbitbucket.pipelines.runner.scheduled.state.update.initial.delay.seconds=0 \ -Dbitbucket.pipelines.runner.scheduled.state.update.period.seconds=30 \ -Dfile.encoding=UTF-8 \ -Dsun.jnu.encoding=UTF-8 \ ./runner.jar