observe-lens-pipelines

Read CI pipelines read-only to explain what a build, test run or workflow did and why: Jenkins jobs and builds, GitHub Actions workflows, runs, jobs and steps, their logs, parameters, artifacts and JUnit or Allure test reports, compared run to run. Use this whenever the user pastes a Jenkins or GitHub Actions URL or a run or build number, asks why a pipeline, build, test, sanity or regression run failed or is flaky, which commit or image a run produced, whether a merge or fix passed CI, or what changed between two runs, even if they do not say Jenkins, GitHub Actions or CI. Read-only: it never triggers, reruns, cancels or approves anything; it tells the user how. Not for writing or editing pipeline files, and for what is deployed where use observe-lens-cd.

Version

1.0.1

License

Apache-2.0

Compatibility

Python 3.11+ (standard library only) on macOS, Linux or Windows, network access to the CI server, and an instance in ~/.config/observe-lens/pipelines (see references/setup.md).