Skip to main content
Gitar reads failed Concourse steps and explains the failure on the PR. Concourse reports a build result to the PR as a status. That status links to the build, and Gitar fetches the logs from the configured server.
See Platform support for code-host availability.

​
Prerequisites

  • Connect the repository to Gitar and enable CI failure analysis.
  • Confirm Concourse reports build results to the PR. For VCS integration, see Concourse’s resources documentation and resource types directory.
  • Make the Concourse server reachable from Gitar over HTTPS, with a valid certificate. See Network access for servers on private networks.
  • Ask a Concourse administrator to create a dedicated local user and grant viewer access to the teams Gitar should read.
  • Keep a completed private build with archived logs available for connection validation. A successful or failed build works.

​
Setup

1

Prepare a viewer account

Create a dedicated local user and assign the viewer role on each permitted team.Use that account’s local username and password in Gitar. An SSO login or a copied fly session token cannot replace these credentials. With viewer access, Gitar reads private build logs without starting builds or changing pipelines.
2

Connect the server in Gitar

Open the Gitar organization’s Settings > Integrations, find Concourse, and click Connect.Click Validate and save. Gitar checks access to the build’s logs before saving the connection.Each connection holds its own server address and password. Repeat this step for another server. To change a server already listed, use Edit connection.

​
Manage credentials

Use Edit connection to save a rotated password, then validate against a completed private build. Leave Password blank to reuse the stored password when the server URL and username are unchanged. Changing either requires entering a password. Use Disconnect to remove that server’s configuration and saved credential from Gitar. To revoke the account itself, remove its team access or disable it in Concourse.

​
What Gitar reads

Once connected, Gitar automatically reads failed-step logs and posts an analysis on the PR. It clears the failure analysis when CI recovers. Gitar writes nothing back to Concourse. Starting or retrying a build through Gitar is not supported. See CI failure analysis.

​
Troubleshooting

Confirm the username is a local Concourse user, the password is correct, and that user has viewer access to the build’s team. Add the exact team name to Permitted teams.Use a completed build whose archived logs still exist. A running build can exceed the validation timeout. An SSO-only account cannot authenticate through this connection form.
Copy the build link from the same server saved in Server URL. Check the HTTPS hostname, port and base path. An alias or redirect to another address does not count as a match.
Check the PR for a failing status on its head commit with a Concourse build link. If no status appears, check the pipeline’s VCS integration using Concourse’s resource types directory.Confirm the matching Concourse connection is saved and that CI failure analysis is enabled for the repository. If logs have been pruned, run another build and test with its URL.
Confirm Gitar can reach the HTTPS endpoint and trust its certificate. A browser session on a company VPN does not prove Gitar has access. See Network access.