Details
-
Improvement
-
Status: Reopened (View Workflow)
-
Major
-
Resolution: Unresolved
-
b19
-
-
Pipeline - July/August
Description
I noticed this while filing another ticket (JENKINS-41496), but the "Changes" view for the Pipeline run for this project "azure" has the "wrong commits" shown. See the screenshots for more.
What basically appears to be happening is that any change to a Shared Library will result in newly triggered Pipelines which have "Poll SCM" configured. Pipelines which configure a timer will also have Changes from the Shared Library listed when it executes again.
I think listing the Shared Library commits in "Changes" is acceptable, but triggering based on an SCM Poll for a Pipeline is very confusing behavior and IMHO incorrect behavior.
As a shared tooling team, I would not expect my Shared Library changes to trigger a bunch of Pipelines for projects depending on them.
Attachments
Issue Links
- is duplicated by
-
JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs
-
- Reopened
-
-
JENKINS-39499 There is no way to set changeSet property of shared library checkout to false
-
- Resolved
-
-
JENKINS-42067 Any commit to common library SCM repository triggers all pipeline build plans
-
- Resolved
-
-
JENKINS-42320 pipeline shared library changes repeatedly trigger failing jobs
-
- Resolved
-
-
JENKINS-41442 Configuring Pipeline Global Library injects History into Job.
-
- Resolved
-
-
JENKINS-45133 Option to remove global library changes from builds changes list
-
- Resolved
-
- relates to
-
JENKINS-38659 CpsScmFlowDefinition changelog and poll configuration
-
- Open
-
-
JENKINS-65649 disable Include @Library changes in job recent changes is not respected
-
- Open
-
-
JENKINS-42320 pipeline shared library changes repeatedly trigger failing jobs
-
- Resolved
-
-
JENKINS-42809 Activity/Branch dashboard show pipeline library commit instead of actual built commit
-
- Closed
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | classic-changes-view.png [ 35641 ] | |
Component/s | pipeline [ 21692 ] | |
Component/s | blueocean-plugin [ 21481 ] | |
Description |
I noticed this while filing another ticket ( I'm not sure why. |
I noticed this while filing another ticket ( What basically appears to be happening is that any change to a Shared Library will result in _newly_ triggered Pipelines which have "Poll SCM" configured. Pipelines which configure a timer will also have Changes from the Shared Library listed when it executes again. I think *listing* the Shared Library commits in "Changes" is acceptable, but *triggering* based on an SCM Poll for a Pipeline is very confusing behavior and IMHO incorrect behavior. As a shared tooling team, I would not expect my Shared Library changes to trigger a bunch of Pipelines for projects depending on them. |
Priority | Major [ 3 ] | Minor [ 4 ] |
Summary | Blue Ocean "Changes" for a Pipeline are from the completely wrong repository | Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries |
Component/s | workflow-cps-global-lib-plugin [ 21714 ] | |
Component/s | workflow-job-plugin [ 21716 ] | |
Component/s | workflow-scm-step-plugin [ 21717 ] | |
Component/s | pipeline [ 21692 ] |
Component/s | workflow-job-plugin [ 21716 ] | |
Component/s | workflow-scm-step-plugin [ 21717 ] | |
Issue Type | Bug [ 1 ] | Improvement [ 4 ] |
Link |
This issue is duplicated by |
Link | This issue is duplicated by JENKINS-39615 [ JENKINS-39615 ] |
Link |
This issue is duplicated by |
Link |
This issue relates to |
Link | This issue relates to JENKINS-38659 [ JENKINS-38659 ] |
Issue Type | Improvement [ 4 ] | Bug [ 1 ] |
Issue Type | Bug [ 1 ] | Improvement [ 4 ] |
Link |
This issue relates to |
Remote Link | This issue links to "PR 34 (Web Link)" [ 16918 ] |
Labels | cloudbees-internal-pipeline |
Priority | Minor [ 4 ] | Major [ 3 ] |
Sprint | Pipeline - July/August [ 371 ] |
Assignee | Andrew Bayer [ abayer ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Link |
This issue is duplicated by |
Attachment | global-pipeline-configuration.png [ 39811 ] | |
Attachment | triggered-build-log.png [ 39812 ] |
Link |
This issue is duplicated by |
Link |
This issue is duplicated by |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Comment |
[ I see this issue again on plugin 2.9 and Jenkins 2.107.2. Does someone knows if this can be solved somehow? ] |
Comment | [ This is a pretty significant issue. We've removed our Global Pipeline Library config, restarted jenkins and it's still triggering events ] |
Attachment | image-2019-04-08-13-45-36-893.png [ 46656 ] |
Assignee | Andrew Bayer [ abayer ] |
Link | This issue relates to JENKINS-65649 [ JENKINS-65649 ] |
Could you please paste the JSON response from the REST API call to .../runs/$runId?