" templates : - name : whalesay container : image : docker/whalesay:latest command : args : When and how does selector concurrency configuration work? For information on Go templates and Sprig functions, see the Go template package documentation, and Sprig Function Documentation. The parameter mapping format must confirm to Sprig templates. The template is the parameter mapping for the name, that is resolved to the selector value when the pipeline is run.The name is any meaningful/logical name that describes the selector.Here’s an example of the ConfigMap with the concurrency definition:ĪpiVersion : v1 kind : ConfigMap metadata : name : semaphore-config data : workflow : " 1" Concurrency selector definitionsĪ concurrency synchronization selector is defined through a name- template pair in workflows or templates: Semaphore synchronization is configured in the ConfigMap, which is referenced from workflows or templates within workflows. This article has examples for semaphore synchronization configurations. And equally important, selectors work with both semaphore and mutex synchronization configurations. Selector-based concurrency configurations support parallel executions of workflows or templates within workflows. Selectors enable access to all workflow properties such as annotations, labels, or parameters using Go template formats. For detailed information, see Synchronization.Ĭodefresh supports an additional level of concurrency synchronization, with selectors, for both workflows and templates. The mechanism enforces this with either semaphore or mutex synchronization configurations. Improve this page on GitHub Selectors for concurrency synchronizationĪrgo Workflows has a synchronization mechanism to limit parallel execution of specific workflows or templates within workflows, as required.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |