I wrote about how to build a pipeline to host multiple Sphinx sites on Azure App Service. But a remaining item is that how to abort a build when nothing (in submodules) is changed.
First we need to detect changes,
- git pull on all submodules to get new commits.
- Use a patch file in master repo to detect changes,
1 2 3 4 5 6 7 8 9 10 11 git checkout master git add -A git status | findstr "working tree clean" if %errorlevel%==0 ( echo no change. abort. powershell -executionpolicy bypass -File abort.ps1 exit /b 0 ) echo change detected. continue.
Most importantly, we execute a PowerShell script to abort.
Well, let’s pause here, and go back to VSTS dashboard to review the status of different builds,
- Some of them succeeded.
- Some were cancelled in the middle by me.
- Some failed due to various errors.
So if we decide to abort a build (when nothing changes), what status should the build look like then?
Your answer to this question, in fact, decides what approach you should do next.
This can be easily achieved, by using the following PowerShell script abort.ps1 ,
1 2 Write-Host "##vso[task.setvariable variable=agent.jobstatus;]canceled" Write-Host "##vso[task.complete result=Canceled;]DONE"
It simply tells the agent to cancel the task. Miserably, you notice that on dashboard the build is displayed as succeeded. Anyway, it works.
Update: This approach no longer works in newer releases, and the error message is Overwriting readonly variable ‘agent.jobstatus’ is not permitted.
It is rather simple to achieve, because you simply need to modify the batch file as
1 2 3 4 5 6 7 8 9 10 git checkout master git add -A git status | findstr "working tree clean" if %errorlevel%==0 ( echo no change. abort. exit /b 1 ) echo change detected. continue.
A non-zero return code is enough to fail the task and the whole build.
If you intend to see the aborted build as cancelled, things go complicated, and we need to call VSTS REST API with some special credentials.
I created a PowerShell script on GitHub to guide you.
Generally speaking, you need to create a special personal access token, add it to the pipeline as secret, and then pass it on to the script. The step-by-step guide can be found in the GitHub repo.
Once aborted, the build is showed as cancelled in VSTS dashboard, just like other builds you cancelled manually.
Another remaining challenge is how to properly handle private repo in pipeline, for which I wrote another post.