Setting up alerts¶
calcite can communicate and send notifications through various channels.
To configure alerts, simply visit the
Alerts page of your project.
Triggering a workflow¶
npx @siliceum/calcite-cli [command arguments]allows you to quickly test the calcite CLI.
calcite upload, you will need to provide the project token.
Then you can use the following command:
calcite trigger <baseline commit id>.
This will trigger a workflow against the provided baseline commid it.
For now, the baseline commit id must be the full commit id, not an alias or the abbreviated version. In the future, you will be able to use any git reference.
be790bd73does NOT work
v1.2.0does NOT work
refs/heads/masterdoes NOT work
masterdoes NOT work
You can also specify more information via additional arguments:
- calcite trigger [options] <baseline_id> [target_id]
Triggers a calcite workflow for the given baseline (previous) and target (new) commits, using their full commit sha. This is used once all datasets were uploaded to trigger notifications.
- -u, --url <server url>
Set the target server url, for preview and enterprise users. The CALCITE_URL environment variable can also be used, otherwise it will be set to the public server.
- -t, --token <token id>
Set the project token. By default the CALCITE_TOKEN environment variable is used.
- -tt, --triggertags <taglist>
Comma seperated list of tags for this workflow. This is used as a filter for alerts.
- -PR, --pullRequestId <id>
Specify the pull request number.
- -h, --help
display help for command