> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/install/ci-tracer.md).

# Lunar CI Tracer

Which CI platforms the Lunar CI Tracer can trace (GitHub Actions, Buildkite, and GitLab CI), and where the setup instructions for each live.

The **Lunar CI Tracer** instruments your CI runners: it wraps the runner process, watches what a build actually does, and triggers collectors at the right moments. That is how build-time facts reach the Hub, including test results, scan output, image digests, and deploy markers.

It installs on your runners rather than in the cluster, so it is independent of the Hub install and can be added at any point after it.

CI tracing is optional. Lunar still collects from pushes and merge requests without it; the tracer is what adds the build-time half.

| CI platform        | Support                                        | Setup                                                                                                                                                                                                                                         |
| ------------------ | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GitHub Actions** | Supported                                      | [Self-hosted runners](/install/ci-tracer/github-actions-self-hosted.md): install the tracer on the runner. [GitHub-managed runners](/install/ci-tracer/github-actions-managed.md): add the `earthly/lunar-ci-tracer` action to your workflow. |
| **Buildkite**      | Supported                                      | [Buildkite](/install/ci-tracer/buildkite.md): an agent command hook plus a Notification Service webhook.                                                                                                                                      |
| **GitLab CI**      | [Coming soon](/install/ci-tracer/gitlab-ci.md) | Nothing to install yet. Submit build-time facts from a job with [`lunar collect`](/docs/lunar-cli.md#lunar-collect) in the meantime.                                                                                                          |

## Choosing between the two GitHub Actions options

Both put the same tracer on the runner; they differ in where the install happens.

* [**The action**](/install/ci-tracer/github-actions-managed.md) is per workflow job, and works on GitHub-hosted *and* self-hosted runners. It is the easier starting point, and the only option when you do not control the runner image.
* [**Installing on the runner**](/install/ci-tracer/github-actions-self-hosted.md) is per-machine, so every workflow on that runner is traced without touching any workflow YAML. It needs self-hosted runners you administer.

## Shared configuration

* [Configuration reference](/install/ci-tracer/configuration-reference.md) covers every environment variable the tracer reads, on any platform.
* [CI job identity](/docs/authorization/ci-identity.md) covers running without the shared Hub service token, on the OIDC token GitHub Actions or GitLab CI issues to the job.
* [Systemd](/install/ci-tracer/systemd.md) covers running the tracer as a service on a Linux host.

## Next steps

* [Git Platforms](/install/git-platforms.md) for the credentials Lunar uses to read repositories and post results.
* [Install Lunar](/install.md) for where CI integration fits in the overall install.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-lunar.earthly.dev/install/ci-tracer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.