Windows runner as a scheduled task

[alandoe (Alan Doering)]

Sonarqube Version 10.0 (build 68432)
Windows Runner v1.421

— Contents of powerscript ps1 file follow:
#Invoke-WebRequest -Uri https://product-downloads.atlassian.com/software/bitbucket/pipelines/atlassian-bitbucket-pipelines-runner-1.421.zip -OutFile .\atlassian-bitbucket-pipelines-runner.zip
#Expand-Archive .\atlassian-bitbucket-pipelines-runner.zip
cd C:\Users\adoering\Desktop\atl\bin
.\start.ps1 -accountUuid ‘{d24a6703-fa0d-4b08-aec1-f291a0ebdd8f}’ -runnerUuid ‘{2aec5f38-d1d8-5b2b-b72e-4d284f362b99}’ -OAuthClientId u3zFBgpJKHJAe5gygjwb99xTy7yQsWka -OAuthClientSecret ATOATlciRHy3dg5CeF4TL4tcn4Jfxv1b77PfQiQ-AEmKOKahqTZd498Fa-h7rLELsRDDC900A823 -workingDirectory ‘e:\temp’
pause
— End Ps1 contents

Sonarqube is deployed to our cloud at https://sonarqube.databankcloud.com

My problem is this: The windows Runners works perfectly when executed manually using powershell and the above script.
However, it will not start as a Windows scheduled task using the same script

Is there a document anywhere that explains how to set up the runner as a task that will automatically start whenever the system restarts? Any help is welcomed.

[Colin]

@alandoe

My problem is this: The windows Runners works perfectly when executed manually using powershell and the above script.
However, it will not start as a Windows scheduled task using the same script

I’m not sure what this has to do with SonarQube. This seems like an issue with the Bitbucket runner. Is that right? In that case, you’ll want to get in touch with an Atlassian Community.