[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin

15 views
Skip to first unread message

cleclerc@cloudbees.com (JIRA)

unread,
Aug 5, 2019, 8:48:02 AM8/5/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc created an issue
 
Jenkins / Bug JENKINS-58811
Downstream pipelines not triggered when using Authorize Project Plugin
Issue Type: Bug Bug
Assignee: Cyrille Le Clerc
Components: pipeline-maven-plugin
Created: 2019-08-05 12:47
Priority: Major Major
Reporter: Cyrille Le Clerc

Reported on https://groups.google.com/forum/#!topic/jenkinsci-users/qQxwsrvKjO4

I'm having an issue regarding Jenkins Pipeline Maven Plugin (https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin). It always skips the downstream jobs even if "Build whenever a SNAPSHOT dependency is built" is checked.

Here's the FINER logs for Downstream listener(org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener):

upstreamPipeline (<upstream build>, visibleByDownstreamBuildAuth: false),  downstreamPipeline (<downstream pipeline>, visibleByUpstreamBuildAuth: true), upstreamBuildAuth: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: Username: <user>; Password: [PROTECTED]; 

Skip triggering of <downstream pipeline> by <upstream pipeline> #<build>: downstreamVisibleByUpstreamBuildAuth: true, upstreamVisibleByDownstreamBuildAuth: false

—

The value for visibleByDownstreamBuildAuth is always false. Any ideas how to make that value true?

Also Jenkins has this troubleshooting guide but my settings are already correct.
https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-Mydownstreampipelinesdon'tgettriggeredevenifIuse%22BuildwheneveraSNAPSHOTdependencyisbuilt%22
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

cleclerc@cloudbees.com (JIRA)

unread,
Aug 5, 2019, 8:50:11 AM8/5/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc started work on Bug JENKINS-58811
 
Change By: Cyrille Le Clerc
Status: Open In Progress

cleclerc@cloudbees.com (JIRA)

unread,
Aug 5, 2019, 8:50:11 AM8/5/19
to jenkinsc...@googlegroups.com
Change By: Cyrille Le Clerc
Status: In Progress Review

cleclerc@cloudbees.com (JIRA)

unread,
Aug 5, 2019, 8:51:24 AM8/5/19
to jenkinsc...@googlegroups.com
 

Fixed in 3.8.1
Change By: Cyrille Le Clerc
Status: In Review Resolved
Resolution: Fixed

cleclerc@cloudbees.com (JIRA)

unread,
Aug 16, 2019, 6:09:02 AM8/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc closed an issue as Fixed
Change By: Cyrille Le Clerc
Status: Resolved Closed

maxime.hochet@gmail.com (JIRA)

unread,
Oct 23, 2019, 12:24:01 PM10/23/19
to jenkinsc...@googlegroups.com
Maxime Hochet commented on Bug JENKINS-58811
 
Re: Downstream pipelines not triggered when using Authorize Project Plugin

Hello, I updated the plugin to version 3.8.2.

In the case of multibranch pipeline jobs, it doesn't work. May this ticket be reopen please?

Thanks.
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

cleclerc@cloudbees.com (JIRA)

unread,
Oct 23, 2019, 12:36:03 PM10/23/19
to jenkinsc...@googlegroups.com

Maxime Hochet do you observe a regression between 3.8.1 and 3.8.2? It would be very strange as changes in 3.8.2 are not related at all to these pieces of code.

maxime.hochet@gmail.com (JIRA)

unread,
Oct 23, 2019, 1:05:02 PM10/23/19
to jenkinsc...@googlegroups.com
Maxime Hochet edited a comment on Bug JENKINS-58811
I don't think it is a regression. We have pipeline and multibranch pipeline jobs. For the first ones, it is OK. not the second ones.

Usecase:
* 2 projects: A and B tracked with Git. A is declared as a dependency of B
* 2 multibranch pipelines (with checkboxes checked: 'build if SNAPHSOT dependency is built'): One for A and one for B.


- For each branch I have a job.
- One branch pipeline A builds A as a SNAPSHOT version.
- One branch pipeline B builds B with A as a SNAPSHOT dependency (built from the previous branch pipeline).
* Without Authorize Project Plugin: branch pipeline A triggers B.
* With Authorize Project Plugin: Nothing occurs.
 *

 

 Maybe previous comments are only related to (non multibranch) pipelines jobs?

 

maxime.hochet@gmail.com (JIRA)

unread,
Oct 23, 2019, 1:05:03 PM10/23/19
to jenkinsc...@googlegroups.com

I don't think it is a regression. We have pipeline and multibranch pipeline jobs. For the first ones, it is OK. not the second ones.

Usecase:

  • 2 projects: A and B tracked with Git. A is declared as a dependency of B
  • 2 multibranch pipelines (with checkboxes checked: 'build if SNAPHSOT dependency is built'): One for A and one for B.
  • For each branch I have a job.
  • One branch pipeline A builds A as a SNAPSHOT version.
  • One branch pipeline B builds B with A as a SNAPSHOT dependency (built from the previous branch pipeline).
  • Without Authorize Project Plugin: branch pipeline A triggers B.
  • With Authorize Project Plugin: Nothing occurs.

    Maybe previous comments are only related to (non multibranch) pipelines jobs?

     

    cleclerc@cloudbees.com (JIRA)

    unread,
    Oct 23, 2019, 1:10:03 PM10/23/19
    to jenkinsc...@googlegroups.com
    Cyrille Le Clerc updated an issue
     
    Change By: Cyrille Le Clerc
    Reported on https://groups.google.com/forum/#!topic/jenkinsci-users/qQxwsrvKjO4

    I'm having an issue regarding Jenkins Pipeline Maven Plugin (https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin). It always skips the downstream jobs even if "Build whenever a SNAPSHOT dependency is built" is checked.

    Here's the FINER logs for Downstream listener showing the problem ( enable FINER logs on ` org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener ` ):

    {noformat}

    upstreamPipeline (<upstream build>, visibleByDownstreamBuildAuth: false),  downstreamPipeline (<downstream pipeline>, visibleByUpstreamBuildAuth: true), upstreamBuildAuth: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: Username: <user>; Password: [PROTECTED];

    Skip triggering of <downstream pipeline> by <upstream pipeline> #<build>: downstreamVisibleByUpstreamBuildAuth: true, upstreamVisibleByDownstreamBuildAuth: false
    {noformat}

    ---


    The value for visibleByDownstreamBuildAuth is always false. Any ideas how to make that value true?

    Also Jenkins has this troubleshooting guide but my settings are already correct.
    https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-Mydownstreampipelinesdon'tgettriggeredevenifIuse%22BuildwheneveraSNAPSHOTdependencyisbuilt%22

    cleclerc@cloudbees.com (JIRA)

    unread,
    Oct 23, 2019, 1:12:02 PM10/23/19
    to jenkinsc...@googlegroups.com
    Cyrille Le Clerc commented on Bug JENKINS-58811
     
    Re: Downstream pipelines not triggered when using Authorize Project Plugin

    Maxime Hochet can you please:

    • enable FINER logs on the logger `org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener`
    • run the parent pipeline
    • look at the build console of the triggered parent pipeline and search for messages looking like 
    • upstreamPipeline (<upstream build>, visibleByDownstreamBuildAuth: false),  downstreamPipeline (<downstream pipeline>, visibleByUpstreamBuildAuth: true), upstreamBuildAuth: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: Username: <user>; Password: [PROTECTED]; 

Skip triggering of <downstream pipeline> by <upstream pipeline> #<build>: downstreamVisibleByUpstreamBuildAuth: true, upstreamVisibleByDownstreamBuildAuth: false
    Reply all
    Reply to author
    Forward
    0 new messages