# Continuous integration infrastructure

This page consolidates resources regarding our CI _infrastucture_, namely our [Buildkite agents fleet](#buildkite-agents).
This infrastructure is maintained by the [DevX team](../../../enablement/dev-experience/index.md).

Related resources:

- [CI playbook](../../../process/incidents/playbooks/ci.md)
- [`sourcegraph/sourcegraph` CI pipelines](https://docs.sourcegraph.com/dev/background-information/continuous_integration)
  - [`sourcegraph/sourcegraph` CI dashboard and logs](https://sourcegraph.grafana.net/d/iBBWbxFnk/ci?orgId=1)
  - [Sentry project for CI pipelines](https://sentry.io/organizations/sourcegraph/issues/?project=6110304)

## Buildkite agents

We maintain a shared fleet of Buildkite agents for continuous integration across all repositories.

- [Active agents](https://buildkite.com/organizations/sourcegraph/agents)
- [Terraform and Kubernetes manifests](https://github.com/sourcegraph/infrastructure/tree/main/buildkite)
- Images:
  - [`buildkite-agent`](https://github.com/sourcegraph/infrastructure/tree/main/docker-images/buildkite-agent)
  - [`buildkite-agent-stateless`](https://github.com/sourcegraph/infrastructure/tree/main/docker-images/buildkite-agent-stateless)
  - [`buildkite-job-dispatcher`](https://sourcegraph.com/github.com/sourcegraph/infrastructure/-/tree/docker-images/buildkite-job-dispatcher)
- Specific resources:
  - [Gain access to the CI cluster](../../../process/deployments/debugging/tutorial.md#ci-cluster)
  - [CI playbook](../../../process/incidents/playbooks/ci.md)

### Buildkite agent queues

We have several different types of agents availables. We recommend explicitly declaring which type of agent you want your jobs to run on with the `agents: { queue: "standard" }` field in your pipeline configuration.

The currently available queues:

- `standard`: our default Buildkite agents, currently Docker-in-Docker agents running in Kubernetes
- `vagrant`: special Buildkite agents desgined to run resource intensive test on docker deployments.


<section class="h0Wrapper headingWrapper"><section class="h1Wrapper headingWrapper"><h1 id="continuous-integration-infrastructure"><a class="anchor" aria-hidden tabindex="-1" href="#continuous-integration-infrastructure"><span class="icon icon-link"></span></a>Continuous integration infrastructure</h1>
<p>This page consolidates resources regarding our CI <em>infrastucture</em>, namely our <a href="#buildkite-agents">Buildkite agents fleet</a>.
This infrastructure is maintained by the <a href="../../../enablement/dev-experience/">DevX team</a>.</p>
<p>Related resources:</p>
<ul>
<li><a href="../../../process/incidents/playbooks/ci">CI playbook</a></li>
<li><a href="https://docs.sourcegraph.com/dev/background-information/continuous_integration"><code>sourcegraph/sourcegraph</code> CI pipelines</a>
<ul>
<li><a href="https://sourcegraph.grafana.net/d/iBBWbxFnk/ci?orgId=1"><code>sourcegraph/sourcegraph</code> CI dashboard and logs</a></li>
<li><a href="https://sentry.io/organizations/sourcegraph/issues/?project=6110304">Sentry project for CI pipelines</a></li>
</ul>
</li>
</ul>
<section class="h2Wrapper headingWrapper"><h2 id="buildkite-agents"><a class="anchor" aria-hidden tabindex="-1" href="#buildkite-agents"><span class="icon icon-link"></span></a>Buildkite agents</h2>
<p>We maintain a shared fleet of Buildkite agents for continuous integration across all repositories.</p>
<ul>
<li><a href="https://buildkite.com/organizations/sourcegraph/agents">Active agents</a></li>
<li><a href="https://github.com/sourcegraph/infrastructure/tree/main/buildkite">Terraform and Kubernetes manifests</a></li>
<li>Images:
<ul>
<li><a href="https://github.com/sourcegraph/infrastructure/tree/main/docker-images/buildkite-agent"><code>buildkite-agent</code></a></li>
<li><a href="https://github.com/sourcegraph/infrastructure/tree/main/docker-images/buildkite-agent-stateless"><code>buildkite-agent-stateless</code></a></li>
<li><a href="https://sourcegraph.com/github.com/sourcegraph/infrastructure/-/tree/docker-images/buildkite-job-dispatcher"><code>buildkite-job-dispatcher</code></a></li>
</ul>
</li>
<li>Specific resources:
<ul>
<li><a href="../../../process/deployments/debugging/tutorial#ci-cluster">Gain access to the CI cluster</a></li>
<li><a href="../../../process/incidents/playbooks/ci">CI playbook</a></li>
</ul>
</li>
</ul>
<section class="h3Wrapper headingWrapper"><h3 id="buildkite-agent-queues"><a class="anchor" aria-hidden tabindex="-1" href="#buildkite-agent-queues"><span class="icon icon-link"></span></a>Buildkite agent queues</h3>
<p>We have several different types of agents availables. We recommend explicitly declaring which type of agent you want your jobs to run on with the <code>agents: { queue: "standard" }</code> field in your pipeline configuration.</p>
<p>The currently available queues:</p>
<ul>
<li><code>standard</code>: our default Buildkite agents, currently Docker-in-Docker agents running in Kubernetes</li>
<li><code>vagrant</code>: special Buildkite agents desgined to run resource intensive test on docker deployments.</li>
</ul></section></section></section></section>