PathlyTry Flow

Integration

Pathly GitLab CI components

pathly-ping and pathly-scenario in the GitLab catalog — red pipeline if the smoke fails.

OpenAPI contractIssue an API keyFree Solo account

Full document, no authentication, ready for your client generator.

GitLab CI

Official CI components under gitlab.com/pathly1/provider/gitlab-ci, published in the GitLab CI/CD Catalog (sources in monorepo integrations/gitlab-ci). pathly-ping checks the key; pathly-assert fails if lastStatus ≠ ok; pathly-run triggers and waits; pathly-scenario ensures a Ping. Declare PATHLY_API_TOKEN as a masked / protected project or group variable.

Chain the component after the deploy job (smoke stage). If ping fails, the pipeline turns red before production promotion.

include pathly-assert

# .gitlab-ci.yml
include:
  - component: gitlab.com/pathly1/provider/gitlab-ci/pathly-assert@0.1.2
    inputs:
      api_token: $PATHLY_API_TOKEN
      scenario_id: $PATHLY_SCENARIO_ID

pathly-run (smoke post-deploy)

include:
  - component: gitlab.com/pathly1/provider/gitlab-ci/pathly-run@0.1.2
    inputs:
      api_token: $PATHLY_API_TOKEN
      scenario_id: $PATHLY_SCENARIO_ID
      timeout_sec: "120"

pathly-scenario

include:
  - component: gitlab.com/pathly1/provider/gitlab-ci/pathly-scenario@0.1.2
    inputs:
      api_token: $PATHLY_API_TOKEN
      scenario_name: Checkout
      scenario_url: https://www.example.com/cart
      interval_sec: "300"