Skip to main content
Requires Woodpecker v3.19.0 with its GitHub forge integration.
Gitar reads failed Woodpecker steps and posts the analysis in the GitHub pull request’s dashboard comment.

​
Prerequisites

  • Organization admin access in Gitar.
  • A GitHub repository connected to Gitar with CI failure analysis enabled.
  • A Woodpecker server reachable from Gitar over HTTPS with a valid certificate.
  • A dedicated Woodpecker user that can read pipeline details and archived step logs for the repository.
Woodpecker’s user API token inherits the account’s repository permissions.

​
Connect the server

1

Copy the Woodpecker API token

Sign in to Woodpecker as the dedicated user. Open User settings > CLI and API and copy the API token.
2

Add the server in Gitar

Open Settings > Integrations, find Woodpecker, and select Connect.Select Validate and save. The server appears in the connection list after Gitar validates the token.Select Add another server to connect another Woodpecker instance. Each connection stores its own server URL and token.

​
Manage connections

Leave API token blank to keep the saved token when editing the same server. Changing Server URL requires a token for the new server.

​
Failure analysis

When a pipeline fails, Gitar checks the repository and commit before reading failed-step logs. The pull request’s dashboard comment includes the analysis. Gitar removes the resolved analysis after CI passes. Run or retry pipelines in Woodpecker.

​
Troubleshooting

Confirm the token belongs to the dedicated Woodpecker user. If the token was reset in Woodpecker, save its replacement in Gitar.
Check the pull request for a failed Woodpecker status on its head commit. Its build link must use the same hostname, port and path prefix as the saved Server URL.Confirm the connection is enabled and that the Woodpecker user can read the repository’s archived step logs.
Check the server URL and TLS certificate. Gitar must be able to reach the HTTPS endpoint. See Network access.