Diagnose a failed GitLab pipeline and propose a fix

Olyvr reads the failed job’s logs, finds the likely cause in your local copy of the code, proposes a small change, and files an issue that links to the evidence.

Note

This needs the GitLab plugin to read pipelines and open issues, and the Git and Filesystem plugins to read and change your local code. What Olyvr can do depends on the tools those plugins’ servers offer. Olyvr can only run tests if you have connected a plugin that runs them; otherwise the fix is a proposal, not a tested change.

What you need

• The GitLab plugin signed in with access to the project.
• A local clone of the repository at the failing commit.
• The Filesystem plugin pointed at that folder, and the Git plugin.

Ask Olyvr

Find why the latest pipeline on the payments-api main branch failed, propose the smallest local fix, and create an issue with the evidence. Don’t push, merge or rerun the pipeline.

What Olyvr does

1. Finds the project, pipeline and failed job, and reads the job log.
2. Checks that your local copy is at the same commit, and reads the relevant files.
3. Shows the proposed change as a diff and asks you to approve each file write.
4. Drafts the issue: what failed, the log evidence, the proposed fix, and whether it was tested.
5. Asks you to approve creating the issue, then gives you its link.

Check the result

• The diagnosis matches the failure in the job log, with a link to the job.
• Only the files you approved changed. Your own uncommitted edits are still there; check with git status and git diff.
• The issue says clearly whether the fix was tested.
• Nothing was pushed or merged, and no pipeline was started.

If something goes wrong

• The logs have expired: Olyvr can’t diagnose from them. Rerun the job yourself, then ask again.
• The failure is flaky: expect Olyvr to say the cause is unconfirmed instead of guessing.
• The log contains commands: don’t approve calls you didn’t ask for.