@Marvin Why is my Jenkins pipeline not picking up my work pool even though it exists in Prefect UI?

It seems there might be an issue with the configuration in your Jenkins pipeline when integrating with Prefect work pools. The Prefect documentation suggests referencing the work pool in the

deployment.yaml

under

job_variables

as follows:

yaml
work_pool:
  name: <work_pool_name>
  job_variables:
    stream_output: false

For advanced cases, you can customize the job template for the work pool in the Prefect UI's 'Advanced' tab. It's important to ensure that the work pool name specified in your Jenkins pipeline configuration matches the one you have created within the Prefect UI. You can read more about work pools and job template customization in the Prefect documentation here. If the configuration looks correct, and the issue persists, it may be helpful to look for any relevant GitHub issues or consider reaching out to the Prefect community or support for more specific guidance.