Sorry, no results found for "".
Configuration for different build triggers. You can have different staging and production environments in order to test your site before final deploy
ID of build_trigger
"1822"
Must be exactly "build_trigger".
Name of the build trigger
"Custom build trigger"
The type of build trigger
"custom"
adapter_settings must include the following properties: trigger_url, headers and payload.
adapter_settings must include the following properties: trigger_url, access_token, branch, site_id
adapter_settings must include the following properties: project_id, token, branch, team_id, deploy_hook_url
adapter_settings must include the following properties: project, token, revision, vcs, build_parameters
adapter_settings must include the following properties: trigger_url, token, ref, build_parameters
adapter_settings must include the following properties: api_token, repo, branch, config
Additional settings for the build trigger. The value depends on the adapter.
{
trigger_url: "http://some-url.com/trigger",
headers: { Authorization: "Bearer abc123" },
payload: { type: "build_request" },
}
Timestamp of the last build
"2017-03-30T09:29:14.872Z"
Status of last build
"success"
The URL of the webhook your service has to call when the build completes to report it's status (success or error)
"https://webhooks.datocoms.com/xA1239ajsk123/deploy-results"
Status of Site Search for the frontend
"success"
The public URL of the frontend. If Site Search is enabled (indicated by indexing_enabled), this is the starting point from which the website's spidering will start
"https://www.mywebsite.com/"
Wether Site Search is enabled or not. With Site Search, everytime the website is built, DatoCMS will respider it to get updated content
Wheter an automatic build request to webhook_url should be made on scheduled publications/unpublishings
Unique token for the webhook (it's the same token present in webhook_url)
"xA1239ajsk123"