Provide a Wait/Lock like construct in the Build Worker API for use across multiple concurrent jobs
Subscription has multiple concurrent jobs, Project has a build matrix with 5 configurations to build e.g. spawns 5 build jobs.
The first build job makes changes to files in source control that all other build jobs should wait for prior to cloning and continuing build.
It is possible to roll your own version of this using powershell and some form of remote file or db storage. However, i feel it would be a great feature to add to the Build Worker API, obviously scoped to the current build.
Add-AppveyorWaitLock -Name <string> -Details <string>
Details param would allow some useful information to be shared amongst build jobs
<string> Get-AppveyorWaitLock -Name <string> -Wait <int> -RetryCount <int>
Internally this would Sleep/Retry until the lock is found, or Fail the build if it exceeds the RetryCount
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
1 Posted by Ilya Finkelshte... on 26 Jun, 2018 03:36 AM
Thank you for this scenario. Please watch this issue
2 Posted by Ilya Finkelshte... on 26 Jun, 2018 03:39 AM
Also please check those workarounds:
Ilya Finkelshteyn closed this discussion on 27 Aug, 2018 08:42 PM.