timjones/snapci-resource repository overview

⁠Snap CI Resource for Concourse CI

Tracks Snap CI⁠ piplines for integration with Concourse CI⁠.
Useful when migrating from Snap CI to Concourse CI.

⁠Source Configuration

• owner: Required. The Snap CI build owner.

• repository: Required. The Snap CI build repository.

• user: Required. Your Snap CI user account.

• api_key: Required. Your Snap CI User API Key.

• result_filter: Optional. Only list pipelines that match this result.

• result_stage_filter: Optional. Only list pipeline with a stage that matches this filter, and whose result matches the result_filter.

• branch_name: Optional. The Snap CI build branch name. Defaults to master.

⁠Behavior

⁠check: Checks for Snap CI builds.

Calls the Snap CI pipelines API to iterate over builds in the specified pipeline.

⁠in: Get pipeline JSON data.

Gets the JSON data for the pipeline and saves it to snap_ci.json.

⁠Parameters

• json_file: Optional. Change the file in which to save the JSON pipeline data.

• counter_file: Optional. Output the pipeline counter to the file indicated.

• link_file: Optional. Output the Snap-CI URL of the pipeline to the file indicated.

⁠out: Nothing.

No-op.

⁠Example

resource_types:
- name: snap-ci
  type: docker-image
  source:
    repository: timjones/snapci-resource

resources:
- name: snapci-pipeline
  type: snap-ci
  source:
    owner: ProjectOwner
    repository: some-repo
    branch_name: master
    user: Me
    api_key: MySnapCiAPIKey

jobs:
- name: run-end-to-end-tests
  plan:
  - get: snapci-pipeline
    trigger: true
  - task: run-tests
    config:
      ...