Merge branch 'obicke-master-patch-0ffe' into 'master'

Adding guidance for Jenkins to GitLab workflow

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136892



Merged-by: Marcel Amirault <mamirault@gitlab.com>
Approved-by: Jackie Porter <jporter@gitlab.com>
Approved-by: Marcel Amirault <mamirault@gitlab.com>
Reviewed-by: Marcel Amirault <mamirault@gitlab.com>
Reviewed-by: Omar Bickell <obickell@gitlab.com>
Co-authored-by: Omar Bickell <obickell@gitlab.com>

doc/integration/jenkins.md

@@ -18,6 +18,12 @@ You should use a Jenkins integration with GitLab when:
 - You're invested in [Jenkins plugins](https://plugins.jenkins.io/) and choose
   to keep using Jenkins to build your apps.
 
+This integration can trigger a Jenkins build when a change is pushed to GitLab.
+
+You cannot use this integration to trigger GitLab CI/CD pipelines from Jenkins. Instead,
+use the [pipeline triggers API endpoint](../api/pipeline_triggers.md) in a Jenkins job,
+authenticated with a [pipeline trigger token](../ci/triggers/index.md#create-a-pipeline-trigger-token).
+
 After you have configured a Jenkins integration, you trigger a build in Jenkins
 when you push code to your repository or create a merge request in GitLab. The
 Jenkins pipeline status displays on merge request widgets and the GitLab