> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jenkins

> Use a Jenkins shell step to call the Cloudgeni scan API directly and keep your pipeline integration explicit.

# Jenkins

Jenkins can integrate with Cloudgeni through a plain shell step.

That is the most honest way to document the current product surface: Jenkins is a caller of the
public API, not a special first-party plugin.

## Static Analysis Example

```groovy theme={null}
pipeline {
  agent any

  stages {
    stage('Cloudgeni Static Analysis') {
      steps {
        sh '''
          curl --fail --silent --show-error \
            -X POST \
            -H "Content-Type: application/json" \
            -H "X-CLOUDGENI-API-KEY: ${CLOUDGENI_API_KEY}" \
            "${CLOUDGENI_API_URL}/api/v1/organizations/${CLOUDGENI_ORG_ID}/workspaces/${CLOUDGENI_WORKSPACE_ID}/repositories/${CLOUDGENI_REPO_ID}/static-analysis" \
            -d '{"analysisEngine":"checkov","excludedPaths":[]}'
        '''
      }
    }
  }
}
```

## Next

Use [Scanning API](/api-reference/scanning-api) for the full set of scan endpoints and response
patterns.