cubrid-ci-trigger
Trigger CUBRID CI on a PR
Post a /run ... comment on a CUBRID GitHub PR. The CI bot parses the comment body and launches the named CircleCI suites against the PR's current head commit — not your local working tree.
Suite selection
| Comment body | Suites launched |
|---|---|
/run sql medium |
ci/circleci: test_sql, ci/circleci: test_medium |
/run all |
sql, medium, and shell suites |
These two bodies are the verified, known-good forms — both are in production use on CUBRID PRs. The grammar appears to be /run plus space-separated suite tokens, so combos like /run shell may work, but they are unverified: prefer mapping the user's request to one of the two known-good forms, and if you do post an unverified combo, watch pickup closely (Step 5) and fall back to a known-good form if the suites never start.
When the user doesn't name suites, default to /run sql medium: shell is by far the slowest suite, so reserve /run all for when the user asks for it or the change touches shell-tested behavior.
Step 1: Resolve the PR
If $ARGUMENTS contains a PR URL or number, use it; otherwise resolve from the current branch: