The Opsera Pipeline supports webhook based start events for GitLab, GitHub and Bitbucket. With this functionality user can manage what branches the trigger event will occur off of. User can select a primary and secondary branch in this form and any time a commit occurs on one of these branches, the pipeline will be triggered.
...
2. To restrict a Pipeline based webhook trigger to a particular project and branch (master or non-master) select a source repository management Platform from the drop down. Choose from GitLab, GitHub, Bitbucket or BitbucketAzure Devops.
...
3. Upon selecting a Platform, corresponding accounts stored in the Tool Registry will be fetched and provided in the Account drop down. Select the account containing the project you wish to configure your webhook trigger events to.
...
Please Note: If this method is used then this pipeline will be bound to that selected branch activity in order to be triggered. Any activity in other branches or projects for this account will be ignored.
Bitbucket
...
Azure DevOps
| Info |
|---|
Note: If a secondary branch is selected in Source Repository, you must repeat the following steps and select the specific branch in Azure Webhooks |
...
Pipeline Orchestration and Queuing
...
The green ‘Repeat Once’ button will change to ‘Queued Request’
Note: The queued run will ONLY run if the prior pipeline is successful. If prior pipeline fails the queued request will not run.
Cancelling a queued request
...