Currently, pipelines rely on a generic webhook trigger with a shared endpoint. We'd like support for Jenkins' native "Trigger Build Remotely" option at the pipeline level, allowing each pipeline to have its own authentication token and a unique trigger URL in the format:

JENKINS_URL/job/<JOB_NAME>/build?token=<TOKEN>

This would allow different backend services to target specific pipelines directly — without shared endpoints or custom routing logic.

Desired Behavior

Expose a "Trigger Build Remotely" option in pipeline settings.

Allow a per-pipeline authentication token to be defined.

Each pipeline gets its own unique, independently callable trigger URL.