Agree, I created workaround for it:
What we need:
- WinSW - Download to runner folder & rename WinSW.exe to runner.exe
- Configuration file - Save content of XML file as runner.xml
<service>
<id>BitbucketRunnerWrapper</id>
<name>Bitbucket Runner Wrapper (powered by WinSW)</name>
<description>Wrapper for JAVA based Bitbucket Runner</description>
<executable>java</executable>
<arguments>-jar -Dbitbucket.pipelines.runner.account.uuid={xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx} -Dbitbucket.pipelines.runner.repository.uuid={xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx} -Dbitbucket.pipelines.runner.uuid={xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx} -Dbitbucket.pipelines.runner.environment=PRODUCTION -Dbitbucket.pipelines.runner.oauth.client.id=xxxxxxxxxxxxxx -Dbitbucket.pipelines.runner.oauth.client.secret=xxxxxxxxxxxxxxx -Dbitbucket.pipelines.runner.directory.working=..\temp -Dbitbucket.pipelines.runner.runtime=windows-powershell -Dbitbucket.pipelines.runner.scheduled.state.update.initial.delay.seconds=0 -Dbitbucket.pipelines.runner.scheduled.state.update.period.seconds=30 -Dbitbucket.pipelines.runner.cleanup.previous.folders=false -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 ./bin/runner.jar</arguments>
<log mode="roll"></log>
<logpath>%BASE%\logs</logpath>
<stopparentprocessfirst>true</stopparentprocessfirst>
</service>
Dbitbucket.pipelines.runner.account.uuid
Dbitbucket.pipelines.runner.repository.uuid
Dbitbucket.pipelines.runner.uuid
Dbitbucket.pipelines.runner.oauth.client.id
Dbitbucket.pipelines.runner.oauth.client.secret
.\runner.exe install runner.xml
- Go to services and Start the service. Make sure that it runs on proper user.
Any update on this? It's been 3 years without an update. Appreciate there is a valid work around, but this should be a standard option for runners as all other players use it.