v4.3.0

4.3.0 (2021-10-03)

Support CircleCI API v2 🎉

So CircleCI v1.1 does not provide API that about pipeline, previously CIAnalyzer reconstruct pipeline structure from each job.

Now, CIAnalyzer uses a pipeline data structure provided by API v2. The exported data will be closer to what you can see on the CircleCI website.

How to migrate from v1.1

After upgrade CIAnalzyer version newer than v4.2, do not need any changes in your config YAML if you want to still use CircleCI API v1.1 .

When you want to use CircleCI v2, you have to change the config as below.

# before (use API v1.1)
baseUrl: https://circleci.com/api/v1.1

# after (use API v2)
baseUrl: https://circleci.com/api/ # Remove suffix "v1.1" from URL
version: 2 # Add

NOTICE The first time after you enable v2, CIAnalyzer reset the LastRun build number and will export the last 100 pipeline data. As a result, it may be exporting duplicate data that has already been exported before.
There is no workaround to avoid this problem, sorry.

Bug Fixes

• CircleCI: Add baseUrl config validation (58ec9e3)
• CircleCI: CircleCI v2 FETCH_LIMIT up to 100 (44dca7e)
• CircleCI: Ignore pipelines that has not workflows or has on_hold status workflow (91afb51)
• CircleCI: Remediate invalid timestamp in workflows (117d8fb)
• Fix each parseConfig() overwrite argument object (d3398ef)

Features

• CircleCI: Add CircleCI v1 and v2 lastRunStore migration (7916cf7)
• CircleCI: Support CircleCI v2 API (4fbe2d3)

Documents

• fix setup command #352 by @yamatoya