findProjectsForChange/findPackagesForChange
...
functions are not finding my projects
- The most common reason your projects/packages are not being found is the Webhooks Enabled flag is not checked because there is no webhook trigger on the project configured for this stream.
- Ensure the repository name configured in your integration instance in FlexDeploy matches the repository name received from the webhook (case insensitive).
- If a sparse checkout folder is configured on your project, your project will only be detected for a change if one of the modified files from the push event is contained in the sparse checkout folder.
- For example - If you received a push event for a changed file '/content/project1/dist/index.html'. A project with sparse checkout 'content/project2' would not be returned whereas a project with sparse checkout 'content/project1' would be.
How do I create a new Release Snapshot from a webhook build?
- The simplest way is to simply configure a Snapshot Schedule on your release. When the schedule runs it will find the newly built project version which resulted from the webhook.
- A 'createSnapshot' function also exists 'createSnapshot' which can be used within a webhook function.
No webhooks are being received by FlexDeploy (webhook messages screen is blank)
The webhooks may not be getting through because of the firewall. See Webhook Security for options on allowing webhooks to be received by FlexDeploy without sacrificing security.
...