# Jenkins

## Usage

The only **required parameter** for Sleuth is the \*\*name of the Jenkins job \*\*. Sleuth will pass any additional specified parameters to Jenkins when triggering the job in case you are using parameterised builds. See [Jenkins documentation](https://www.jenkins.io/doc/book/using/remote-access-api/) for additional informations.

This example triggers a `deploy-prod` job in Jenkins when code is deployed to the "Staging" environment for more than 4 hours and is healthy:

```
rules:
  - run-deploy:
      conditions:
        - environment='Staging'
        - deployed_for>'4h'
        - health='Healthy'
      actions:
        - trigger_build:
            parameters:
              name: 'deploy-prod'
              my-custom-non-required-param: 'we are going live'
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sleuth.io/sleuth-dora/sleuth-automations/actions/trigger_build/jenkins.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.