cogito.yml

# Names are an homage to https://hanna-barbera.fandom.com/wiki/Cattanooga_Cats

# NOTICE
# In this pipeline we have two cogito resources ONLY BECAUSE this is a test pipeline!
# In a real pipeline, one cogito resource is always enough. If not, please open an
#  issue to discuss your use case.
meta:

  gh-status-1-handlers: &gh-status-1-handlers
    on_success:
      put: gh-status-1
      inputs: [repo.git]
      params: {state: success}
    on_failure:
      put: gh-status-1
      inputs: [repo.git]
      params: {state: failure}
    on_error:
      put: gh-status-1
      inputs: [repo.git]
      params: {state: error}
    on_abort:
      put: gh-status-1
      inputs: [repo.git]
      params: {state: abort}

  gh-status-2-handlers: &gh-status-2-handlers
    on_success:
      put: gh-status-2
      inputs: [repo.git]
      params: {state: success}
    on_failure:
      put: gh-status-2
      inputs: [repo.git]
      params: {state: failure}
    on_error:
      put: gh-status-2
      inputs: [repo.git]
      params: {state: error}
    on_abort:
      put: gh-status-2
      inputs: [repo.git]
      params: {state: abort}

resource_types:

- name: cogito
  type: registry-image
  # For production use, `24h` is a good tradeoff to get a new release with a maximum delay
  # of 24h. Here we parametrize it to work around a concourse bug when doing development.
  # See CONTRIBUTING for details
  check_every: ((cogito-image-check_every))
  source:
    repository: pix4d/cogito
    tag: ((cogito-tag))

resources:

- name: gh-status-1
  type: cogito
  # Since check is a no-op, we do not check, to reduce load on the system.
  check_every: never
  source:
    # Optional, for debugging only.
    log_level: debug
    owner: ((github-owner))
    repo: ((repo-name))
    access_token: ((oauth-personal-access-token))
    gchat_webhook: ((gchat_webhook))

  # See the NOTICE at the top of this file to understand why we have two cogito resources.
- name: gh-status-2
  type: cogito
  # Since check is a no-op, we do not check, to reduce load on the system.
  check_every: never
  source:
    # Optional, for debugging only.
    log_level: debug
    owner: ((github-owner))
    repo: ((repo-name))
    access_token: ((oauth-personal-access-token))
    gchat_webhook: ((gchat_webhook))
    # These two states make sense only for testing the resource itself...
    chat_notify_on_states: [pending, success]

- name: repo.git
  type: git
  source:
    # If repo is public:
    uri: https://github.com/((github-owner))/((repo-name)).git
    # If repo is private:
    #uri: git@github.com:((github-owner))/((repo-name)).git
    #private_key: ((ssh-key))
    branch: ((branch))

jobs:

  - name: autocat
    <<: *gh-status-1-handlers
    plan:
      - get: repo.git
        trigger: true
      - put: gh-status-1
        inputs: [repo.git]
        params: {state: pending}
      - task: will-fail
        config:
          platform: linux
          image_resource:
            type: registry-image
            source: { repository: alpine }
          run:
            path: /bin/false

  - name: motormouse
    <<: *gh-status-1-handlers
    plan:
      - get: repo.git
        trigger: true
      - put: gh-status-1
        inputs: [repo.git]
        params: {state: pending}
      - task: will-succeed
        config:
          platform: linux
          image_resource:
            type: registry-image
            source: { repository: alpine }
          run:
            path: /bin/true

  - name: kitty-jo
    <<: *gh-status-2-handlers
    plan:
      - get: repo.git
        trigger: true
      - put: gh-status-2
        inputs: [repo.git]
        params:
          state: pending
          gchat_webhook: ((gchat_webhook_2))
      - task: task-1
        config:
          platform: linux
          image_resource:
            type: registry-image
            source: { repository: alpine }
          run:
            path: /bin/true
      - put: gh-status-2
        inputs: [repo.git]
        params:
          # FIXME Here the state doesn't really make sense, because we are in the middle
          #  of a job and there are further tasks: the state could change...
          state: success
          # Override the default build summary with the custom message.
          chat_message: "overriding hello from kitty-jo"
      - task: task-2
        config:
          platform: linux
          image_resource:
            type: registry-image
            source: { repository: alpine }
          run:
            path: /bin/true
      - put: gh-status-2
        inputs: [repo.git]
        params:
          state: success
          # Append the default build summary to the custom message.
          chat_message: "appending hello from kitty-jo"