Source
Pipeline run exports: what to paste and which columns are read
A release pipeline's run history filtered to production: run id, commit or version, the service, finish time and the account that triggered it. The commit or the change reference ties each run to a change; without either, the checker matches on the system and the time.
A header row it reads
the deployment log boxrun id, commit, service, finished at, triggered by, environment
Headers are matched by name, in any order, in any case; CSV, tabs and pipes all work. Times in ISO, US or UK formats are read, and the result states the time zone and the date order it used.
Every column name recognised
60 aliases| Field | Column names read as it |
|---|---|
| deployment id | deployment, deployment id, deploy id, deploy, run, run id, release, release id, build, job, id, pipeline run |
| change reference on the deployment | change, change id, change ref, change reference, pr, pull request, merge request, ticket, ref, reference |
| commit | commit, sha, commit sha, revision, hash, version |
| system | system, repository, repo, application, app, service, component, project, target |
| deployed at | deployed at, deployed, time, timestamp, started, finished, completed, finished at, date, when, deploy time, completed at |
| deployed by | deployed by, by, user, actor, triggered by, initiated by, deployer, operator |
| environment (non-production rows are shown, not read for findings) | environment, env, stage |