learning_circleci.md

path	title
/learnings/circleci	Learnings: CircleCI

Table Of Contents

• Path filtering orb
  • Silly example
  • Limits

Path filtering orb

Silly example

config.yml:

version: 2.1
setup: true

orbs:
  path-filtering: circleci/[email protected]

werkflows:
  setup:
    jobs:
      - path-filtering/filter:
          base-revision: main
          config-map: .circleci/extra-config.yml
          mapping: |
            regex-we-match-log-lines-against/.* parameter-name-but-can-be-only-one "value json literal"

the "value json literal" spot can be any JSON literal: strings (yes, including the quotes), true/false, numbers. Not arrays, Circle doesn't support an array type I don't know what would happen here.

extra-config.yml

version: 2.1


parameters:
  parameter-name-but-can-be-only-one:
    type: string
    default: ''

jobs:
  build-it:
    parameters:
      my-parameter:
        type: string

    steps:
      - run: echo "<< parameters.my-parameter >>"

workflows:
  build-it:
    jobs:
      - my-parameter:
          name: "build << pipeline.parameters.parameter-name-but-can-be-only-one >>"

Will result in - if any files (matching that first regex, in this case files in the regex-we-match-log-lines-against folder - to echo "value json literal".

Limits

1. If you set the same parameter in multiple lines in your mapping file the last set wins. (Which will be the last set? Undefined behavior). Thus usually you map each folder to a unique pipeline parameter and use that to turn on or off sections of your pipeline

2. You only get one continuation per