subject:"Jenkins Pipeline Maven Plugin \- Always skipping downstream job"

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-05 Thread Cyrille Le Clerc

You're welcome

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4c028c32-1faa-4ddb-af19-3ae20295b4cc%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-04 Thread drpm

Hello, 

Sorry for late response. I tested the new release and it worked :) It's now 
using the SYSTEM user instead of anonymous.

upstreamPipeline (, visibleByDownstreamBuildAuth: true),  
> downstreamPipeline (, visibleByUpstreamBuildAuth: true), 
> upstreamBuildAuth: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
> null; Not granted any authorities


isUpstreamBuildVisibleByDownstreamBuildAuth(upstreamPipeline: , 
> downstreamPipeline: <>): downstreamPipelineAuth: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
> null; Not granted any authorities, 
> upstreamPipelineObtainedAsImpersonated:org.jenkinsci.plugins.workflow.job.WorkflowJob@151406db[upstream
>  
> job], result: true


Thank you!


On Monday, August 5, 2019 at 3:10:49 AM UTC+9, Cyrille Le Clerc wrote:
>
> @drpm can you please verify that version 3.8.1 fixes your problem of 
> downstream pipelines not being triggered when using the Authorize Project 
> Plugin
>
>
> https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.8.1
>
> On Friday, August 2, 2019 at 4:04:26 PM UTC+2, Cyrille Le Clerc wrote:
>>
>> @drpm can you test 
>> https://github.com/jenkinsci/pipeline-maven-plugin/pull/224 ?
>>
>> @daniel could you kindly review the code of 
>> https://github.com/jenkinsci/pipeline-maven-plugin/pull/224 it is a 
>> simple change ?
>>
>> On Friday, August 2, 2019 at 12:12:01 PM UTC+2, Cyrille Le Clerc wrote:
>>>
>>> Thank you very much Daniel, I'll have a look
>>>
>>> On Friday, August 2, 2019 at 12:04:04 PM UTC+2, Daniel Beck wrote:



 > On 2. Aug 2019, at 11:49, Cyrille Le Clerc  
 wrote: 
 > 
 > Do you understand why the downstream pipeline is seen as 
 unauthenticated? Could there be a configuration glitch on your setup? 
 > 

 My guess, not having debugged this further: 

 Pipeline Maven Plugin seems to have copied code from 
 ReverseBuildTrigger in core (see your code snippet, 'cf. BuildTrigger') 
 that wasn't adapted to JENKINS-22949 in 
 https://jenkins.io/changelog/#v2.62 

 See 
 https://github.com/jenkinsci/jenkins/commit/915543dca5399d3ba052219ddfe9c3c061e70726
  
 for the change -- there's no need to set the auth to ANONYMOUS anymore if 
 it's SYSTEM otherwise. 



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a4733407-258c-4524-b7aa-daa8cfc3c657%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-04 Thread Cyrille Le Clerc

@drpm can you please verify that version 3.8.1 fixes your problem of 
downstream pipelines not being triggered when using the Authorize Project 
Plugin

https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.8.1

On Friday, August 2, 2019 at 4:04:26 PM UTC+2, Cyrille Le Clerc wrote:
>
> @drpm can you test 
> https://github.com/jenkinsci/pipeline-maven-plugin/pull/224 ?
>
> @daniel could you kindly review the code of 
> https://github.com/jenkinsci/pipeline-maven-plugin/pull/224 it is a 
> simple change ?
>
> On Friday, August 2, 2019 at 12:12:01 PM UTC+2, Cyrille Le Clerc wrote:
>>
>> Thank you very much Daniel, I'll have a look
>>
>> On Friday, August 2, 2019 at 12:04:04 PM UTC+2, Daniel Beck wrote:
>>>
>>>
>>>
>>> > On 2. Aug 2019, at 11:49, Cyrille Le Clerc  
>>> wrote: 
>>> > 
>>> > Do you understand why the downstream pipeline is seen as 
>>> unauthenticated? Could there be a configuration glitch on your setup? 
>>> > 
>>>
>>> My guess, not having debugged this further: 
>>>
>>> Pipeline Maven Plugin seems to have copied code from ReverseBuildTrigger 
>>> in core (see your code snippet, 'cf. BuildTrigger') that wasn't adapted to 
>>> JENKINS-22949 in https://jenkins.io/changelog/#v2.62 
>>>
>>> See 
>>> https://github.com/jenkinsci/jenkins/commit/915543dca5399d3ba052219ddfe9c3c061e70726
>>>  
>>> for the change -- there's no need to set the auth to ANONYMOUS anymore if 
>>> it's SYSTEM otherwise. 
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/85bd263e-2a8e-4eb7-8c57-a51992c638b3%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-02 Thread Cyrille Le Clerc

@drpm can you test 
https://github.com/jenkinsci/pipeline-maven-plugin/pull/224 ?

@daniel could you kindly review the code of 
https://github.com/jenkinsci/pipeline-maven-plugin/pull/224 it is a simple 
change ?

On Friday, August 2, 2019 at 12:12:01 PM UTC+2, Cyrille Le Clerc wrote:
>
> Thank you very much Daniel, I'll have a look
>
> On Friday, August 2, 2019 at 12:04:04 PM UTC+2, Daniel Beck wrote:
>>
>>
>>
>> > On 2. Aug 2019, at 11:49, Cyrille Le Clerc  
>> wrote: 
>> > 
>> > Do you understand why the downstream pipeline is seen as 
>> unauthenticated? Could there be a configuration glitch on your setup? 
>> > 
>>
>> My guess, not having debugged this further: 
>>
>> Pipeline Maven Plugin seems to have copied code from ReverseBuildTrigger 
>> in core (see your code snippet, 'cf. BuildTrigger') that wasn't adapted to 
>> JENKINS-22949 in https://jenkins.io/changelog/#v2.62 
>>
>> See 
>> https://github.com/jenkinsci/jenkins/commit/915543dca5399d3ba052219ddfe9c3c061e70726
>>  
>> for the change -- there's no need to set the auth to ANONYMOUS anymore if 
>> it's SYSTEM otherwise. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/090a4939-84f7-42c2-b94e-07c45d557b67%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-02 Thread Cyrille Le Clerc

Thank you very much Daniel, I'll have a look

On Friday, August 2, 2019 at 12:04:04 PM UTC+2, Daniel Beck wrote:
>
>
>
> > On 2. Aug 2019, at 11:49, Cyrille Le Clerc  > wrote: 
> > 
> > Do you understand why the downstream pipeline is seen as 
> unauthenticated? Could there be a configuration glitch on your setup? 
> > 
>
> My guess, not having debugged this further: 
>
> Pipeline Maven Plugin seems to have copied code from ReverseBuildTrigger 
> in core (see your code snippet, 'cf. BuildTrigger') that wasn't adapted to 
> JENKINS-22949 in https://jenkins.io/changelog/#v2.62 
>
> See 
> https://github.com/jenkinsci/jenkins/commit/915543dca5399d3ba052219ddfe9c3c061e70726
>  
> for the change -- there's no need to set the auth to ANONYMOUS anymore if 
> it's SYSTEM otherwise. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/74b51013-9cb7-4bb1-87e4-a4e33bd29f78%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-02 Thread Daniel Beck

> On 2. Aug 2019, at 11:49, Cyrille Le Clerc  wrote:
> 
> Do you understand why the downstream pipeline is seen as unauthenticated? 
> Could there be a configuration glitch on your setup?
> 

My guess, not having debugged this further:

Pipeline Maven Plugin seems to have copied code from ReverseBuildTrigger in 
core (see your code snippet, 'cf. BuildTrigger') that wasn't adapted to 
JENKINS-22949 in https://jenkins.io/changelog/#v2.62

See 
https://github.com/jenkinsci/jenkins/commit/915543dca5399d3ba052219ddfe9c3c061e70726
 for the change -- there's no need to set the auth to ANONYMOUS anymore if it's 
SYSTEM otherwise.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/F1590A34-25AC-4499-BF96-13A93C79F03D%40beckweb.net.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-02 Thread Cyrille Le Clerc

Thanks,

Could you by any chance create a bug on https://issues.jenkins-ci.org with 
the label pipeline-maven-plugin detailing the problem so that it will be 
easier to manage and easier to share knowledge with other users?

Do you understand why the downstream pipeline is seen as unauthenticated? 
Could there be a configuration glitch on your setup?

Cyrille

On Friday, August 2, 2019 at 11:32:57 AM UTC+2, drpm wrote:
>
> Oh It is using the anonymous user for it.
>
> isUpstreamBuildVisibleByDownstreamBuildAuth(org.jenkinsci.plugins.workflow.job.WorkflowJob@3e3adefa[],
>  
>> org.jenkinsci.plugins.workflow.job.WorkflowJob@7b2c0800[]): 
>> taskAuth: 
>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
>> null; Not granted any authorities, downstreamPipelineAuth: 
>> org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@ffc4: 
>> Username: *anonymous*; Password: [PROTECTED]; Authenticated: true; 
>> Details: null; Granted Authorities: anonymous, 
>> upstreamPipelineObtainedAsImpersonated:null, result: false
>>
>
>
> On Friday, August 2, 2019 at 6:15:48 PM UTC+9, Cyrille Le Clerc wrote:
>>
>> Can you please enable FINER 
>> on org.jenkinsci.plugins.pipeline.maven.service.PipelineTriggerService ? I 
>> am interested by the message of 
>> isUpstreamBuildVisibleByDownstreamBuildAuth
>>
>>
>> https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.8.0/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/service/PipelineTriggerService.java#L332
>>
>> public boolean isUpstreamBuildVisibleByDownstreamBuildAuth(@Nonnull 
>>> WorkflowJob upstreamPipeline, @Nonnull Queue.Task downstreamPipeline) {
>>> Authentication auth = 
>>> Tasks.getAuthenticationOf(downstreamPipeline);
>>> Authentication downstreamPipelineAuth;
>>> if (auth.equals(ACL.SYSTEM) && 
>>> !QueueItemAuthenticatorConfiguration.get().getAuthenticators().isEmpty()) {
>>> downstreamPipelineAuth = Jenkins.ANONYMOUS; // cf. 
>>> BuildTrigger
>>> } else {
>>> downstreamPipelineAuth = auth;
>>> }
>>> try (ACLContext ignored = ACL.as(downstreamPipelineAuth)) {
>>> WorkflowJob upstreamPipelineObtainedAsImpersonated = 
>>> getItemByFullName(upstreamPipeline.getFullName(), WorkflowJob.class);
>>> boolean result = upstreamPipelineObtainedAsImpersonated != 
>>> null;
>>> LOGGER.log(Level.FINE, 
>>> "isUpstreamBuildVisibleByDownstreamBuildAuth({0}, {1}): taskAuth: {2}, 
>>> downstreamPipelineAuth: {3}, upstreamPipelineObtainedAsImpersonated:{4}, 
>>> result: {5}",
>>> new Object[]{upstreamPipeline, downstreamPipeline, 
>>> auth, downstreamPipelineAuth, upstreamPipelineObtainedAsImpersonated, 
>>> result});
>>> return result;
>>> }
>>> }
>>
>>
>>
>> On Friday, August 2, 2019 at 1:31:49 AM UTC+2, drpm wrote:
>>>
>>> Hello,
>>>
>>> Thank you for your reply. 
>>>
>>> Yes I do have Jenkins Authorize Project 
>>> plugin. I tried running 
>>> it as a SYSTEM and user with admin privileges and still having the same 
>>> error. 
>>>
>>> *As SYSTEM user: *
>>>

 upstreamPipeline (, visibleByDownstreamBuildAuth: 
 false),  downstreamPipeline (, 
 visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
 org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
 Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
 null; Not granted any authorities
 Skip triggering of  by  
 #: downstreamVisibleByUpstreamBuildAuth: true, 
 upstreamVisibleByDownstreamBuildAuth: false
>>>
>>>
>>>
>>> *As USER WITH PRIV:*
>>>
>>> upstreamPipeline (, visibleByDownstreamBuildAuth: 
 false),  downstreamPipeline (, 
 visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
 org.acegisecurity.providers.UsernamePasswordAuthenticationToken@72da9556: 
 Username: ; Password: [PROTECTED]; Authenticated: 
 true; Details: null; Granted Authorities: authenticated
 Skip triggering of  by  
 #: downstreamVisibleByUpstreamBuildAuth: true, 
 upstreamVisibleByDownstreamBuildAuth: false
>>>
>>>
>>> I also use this plugin: Role+Strategy+Plugin 
>>> 
>>>
>>> Do I need to create a special role? 
>>>
>>> - drpm
>>>
>>> On Friday, August 2, 2019 at 6:02:11 AM UTC+9, Cyrille Le Clerc wrote:

 Hello,

 Could you be using the Jenkins Authorize Project Plugin 
  and impersonate your 
 builds with a user different from SYSTEM? What is the "" displayed 
 in 
 the log message "upstreamPipeline... Username: "?

 When not using the  Jenkins Authorize Project Plugin 
 , the user used to run 
 the ups

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-02 Thread drpm

Oh It is using the anonymous user for it.

isUpstreamBuildVisibleByDownstreamBuildAuth(org.jenkinsci.plugins.workflow.job.WorkflowJob@3e3adefa[],
 
> org.jenkinsci.plugins.workflow.job.WorkflowJob@7b2c0800[]): 
> taskAuth: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
> null; Not granted any authorities, downstreamPipelineAuth: 
> org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@ffc4: 
> Username: *anonymous*; Password: [PROTECTED]; Authenticated: true; 
> Details: null; Granted Authorities: anonymous, 
> upstreamPipelineObtainedAsImpersonated:null, result: false
>


On Friday, August 2, 2019 at 6:15:48 PM UTC+9, Cyrille Le Clerc wrote:
>
> Can you please enable FINER 
> on org.jenkinsci.plugins.pipeline.maven.service.PipelineTriggerService ? I 
> am interested by the message of 
> isUpstreamBuildVisibleByDownstreamBuildAuth
>
>
> https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.8.0/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/service/PipelineTriggerService.java#L332
>
> public boolean isUpstreamBuildVisibleByDownstreamBuildAuth(@Nonnull 
>> WorkflowJob upstreamPipeline, @Nonnull Queue.Task downstreamPipeline) {
>> Authentication auth = 
>> Tasks.getAuthenticationOf(downstreamPipeline);
>> Authentication downstreamPipelineAuth;
>> if (auth.equals(ACL.SYSTEM) && 
>> !QueueItemAuthenticatorConfiguration.get().getAuthenticators().isEmpty()) {
>> downstreamPipelineAuth = Jenkins.ANONYMOUS; // cf. 
>> BuildTrigger
>> } else {
>> downstreamPipelineAuth = auth;
>> }
>> try (ACLContext ignored = ACL.as(downstreamPipelineAuth)) {
>> WorkflowJob upstreamPipelineObtainedAsImpersonated = 
>> getItemByFullName(upstreamPipeline.getFullName(), WorkflowJob.class);
>> boolean result = upstreamPipelineObtainedAsImpersonated != 
>> null;
>> LOGGER.log(Level.FINE, 
>> "isUpstreamBuildVisibleByDownstreamBuildAuth({0}, {1}): taskAuth: {2}, 
>> downstreamPipelineAuth: {3}, upstreamPipelineObtainedAsImpersonated:{4}, 
>> result: {5}",
>> new Object[]{upstreamPipeline, downstreamPipeline, 
>> auth, downstreamPipelineAuth, upstreamPipelineObtainedAsImpersonated, 
>> result});
>> return result;
>> }
>> }
>
>
>
> On Friday, August 2, 2019 at 1:31:49 AM UTC+2, drpm wrote:
>>
>> Hello,
>>
>> Thank you for your reply. 
>>
>> Yes I do have Jenkins Authorize Project 
>> plugin. I tried running it 
>> as a SYSTEM and user with admin privileges and still having the same error. 
>>
>> *As SYSTEM user: *
>>
>>>
>>> upstreamPipeline (, visibleByDownstreamBuildAuth: 
>>> false),  downstreamPipeline (, 
>>> visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
>>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>>> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
>>> null; Not granted any authorities
>>> Skip triggering of  by  
>>> #: downstreamVisibleByUpstreamBuildAuth: true, 
>>> upstreamVisibleByDownstreamBuildAuth: false
>>
>>
>>
>> *As USER WITH PRIV:*
>>
>> upstreamPipeline (, visibleByDownstreamBuildAuth: 
>>> false),  downstreamPipeline (, 
>>> visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
>>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@72da9556: 
>>> Username: ; Password: [PROTECTED]; Authenticated: 
>>> true; Details: null; Granted Authorities: authenticated
>>> Skip triggering of  by  
>>> #: downstreamVisibleByUpstreamBuildAuth: true, 
>>> upstreamVisibleByDownstreamBuildAuth: false
>>
>>
>> I also use this plugin: Role+Strategy+Plugin 
>> 
>>
>> Do I need to create a special role? 
>>
>> - drpm
>>
>> On Friday, August 2, 2019 at 6:02:11 AM UTC+9, Cyrille Le Clerc wrote:
>>>
>>> Hello,
>>>
>>> Could you be using the Jenkins Authorize Project Plugin 
>>>  and impersonate your 
>>> builds with a user different from SYSTEM? What is the "" displayed in 
>>> the log message "upstreamPipeline... Username: "?
>>>
>>> When not using the  Jenkins Authorize Project Plugin 
>>> , the user used to run 
>>> the upstream pipelines is SYSTEM as we can see in the sample below
>>>
>>> upstreamPipeline (plugins/pipeline-maven-plugin/dependency-graph/my-jar, 
 visibleByDownstreamBuildAuth: true),  downstreamPipeline 
 (plugins/pipeline-maven-plugin/dependency-graph/my-war-multibranch/master, 
 visibleByUpstreamBuildAuth: true), *upstreamBuildAuth*: 
 org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
 *Username: 
 SYSTEM*; Password: [PROTECTED]; Authenticated: false; Details: null; 
 Not granted any authorities
>>>
>>

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-02 Thread Cyrille Le Clerc

Can you please enable FINER 
on org.jenkinsci.plugins.pipeline.maven.service.PipelineTriggerService ? I 
am interested by the message of isUpstreamBuildVisibleByDownstreamBuildAuth

https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.8.0/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/service/PipelineTriggerService.java#L332

public boolean isUpstreamBuildVisibleByDownstreamBuildAuth(@Nonnull 
> WorkflowJob upstreamPipeline, @Nonnull Queue.Task downstreamPipeline) {
> Authentication auth = 
> Tasks.getAuthenticationOf(downstreamPipeline);
> Authentication downstreamPipelineAuth;
> if (auth.equals(ACL.SYSTEM) && 
> !QueueItemAuthenticatorConfiguration.get().getAuthenticators().isEmpty()) {
> downstreamPipelineAuth = Jenkins.ANONYMOUS; // cf. BuildTrigger
> } else {
> downstreamPipelineAuth = auth;
> }
> try (ACLContext ignored = ACL.as(downstreamPipelineAuth)) {
> WorkflowJob upstreamPipelineObtainedAsImpersonated = 
> getItemByFullName(upstreamPipeline.getFullName(), WorkflowJob.class);
> boolean result = upstreamPipelineObtainedAsImpersonated != 
> null;
> LOGGER.log(Level.FINE, 
> "isUpstreamBuildVisibleByDownstreamBuildAuth({0}, {1}): taskAuth: {2}, 
> downstreamPipelineAuth: {3}, upstreamPipelineObtainedAsImpersonated:{4}, 
> result: {5}",
> new Object[]{upstreamPipeline, downstreamPipeline, 
> auth, downstreamPipelineAuth, upstreamPipelineObtainedAsImpersonated, 
> result});
> return result;
> }
> }



On Friday, August 2, 2019 at 1:31:49 AM UTC+2, drpm wrote:
>
> Hello,
>
> Thank you for your reply. 
>
> Yes I do have Jenkins Authorize Project 
> plugin. I tried running it 
> as a SYSTEM and user with admin privileges and still having the same error. 
>
> *As SYSTEM user: *
>
>>
>> upstreamPipeline (, visibleByDownstreamBuildAuth: 
>> false),  downstreamPipeline (, 
>> visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
>> null; Not granted any authorities
>> Skip triggering of  by  #: 
>> downstreamVisibleByUpstreamBuildAuth: true, 
>> upstreamVisibleByDownstreamBuildAuth: false
>
>
>
> *As USER WITH PRIV:*
>
> upstreamPipeline (, visibleByDownstreamBuildAuth: false),  
>> downstreamPipeline (, visibleByUpstreamBuildAuth: 
>> true), upstreamBuildAuth: 
>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@72da9556: 
>> Username: ; Password: [PROTECTED]; Authenticated: 
>> true; Details: null; Granted Authorities: authenticated
>> Skip triggering of  by  #: 
>> downstreamVisibleByUpstreamBuildAuth: true, 
>> upstreamVisibleByDownstreamBuildAuth: false
>
>
> I also use this plugin: Role+Strategy+Plugin 
> 
>
> Do I need to create a special role? 
>
> - drpm
>
> On Friday, August 2, 2019 at 6:02:11 AM UTC+9, Cyrille Le Clerc wrote:
>>
>> Hello,
>>
>> Could you be using the Jenkins Authorize Project Plugin 
>>  and impersonate your 
>> builds with a user different from SYSTEM? What is the "" displayed in 
>> the log message "upstreamPipeline... Username: "?
>>
>> When not using the  Jenkins Authorize Project Plugin 
>> , the user used to run the 
>> upstream pipelines is SYSTEM as we can see in the sample below
>>
>> upstreamPipeline (plugins/pipeline-maven-plugin/dependency-graph/my-jar, 
>>> visibleByDownstreamBuildAuth: true),  downstreamPipeline 
>>> (plugins/pipeline-maven-plugin/dependency-graph/my-war-multibranch/master, 
>>> visibleByUpstreamBuildAuth: true), *upstreamBuildAuth*: 
>>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>>> *Username: 
>>> SYSTEM*; Password: [PROTECTED]; Authenticated: false; Details: null; 
>>> Not granted any authorities
>>
>>
>> Cyrille
>>
>>
>> On Thursday, August 1, 2019 at 9:26:34 AM UTC+2, drpm wrote:
>>>
>>> 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 (, visibleByDownstreamBuildAuth: 
>>> false),  downstreamPipeline (, 
>>> visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
>>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>>> Username: ; Password: [PROTECTED]; *
>>>
>>> *Skip triggering of  by  
>>> #: downstreamVisibleB

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-01 Thread drpm

Hello,

Thank you for your reply. 

Yes I do have Jenkins Authorize Project 
plugin. I tried running it as 
a SYSTEM and user with admin privileges and still having the same error. 

*As SYSTEM user: *

>
> upstreamPipeline (, visibleByDownstreamBuildAuth: false),  
> downstreamPipeline (, visibleByUpstreamBuildAuth: 
> true), upstreamBuildAuth: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
> Username: SYSTEM; Password: [PROTECTED]; Authenticated: false; Details: 
> null; Not granted any authorities
> Skip triggering of  by  #: 
> downstreamVisibleByUpstreamBuildAuth: true, 
> upstreamVisibleByDownstreamBuildAuth: false



*As USER WITH PRIV:*

upstreamPipeline (, visibleByDownstreamBuildAuth: false),  
> downstreamPipeline (, visibleByUpstreamBuildAuth: 
> true), upstreamBuildAuth: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@72da9556: 
> Username: ; Password: [PROTECTED]; Authenticated: 
> true; Details: null; Granted Authorities: authenticated
> Skip triggering of  by  #: 
> downstreamVisibleByUpstreamBuildAuth: true, 
> upstreamVisibleByDownstreamBuildAuth: false


I also use this plugin: Role+Strategy+Plugin 


Do I need to create a special role? 

- drpm

On Friday, August 2, 2019 at 6:02:11 AM UTC+9, Cyrille Le Clerc wrote:
>
> Hello,
>
> Could you be using the Jenkins Authorize Project Plugin 
>  and impersonate your 
> builds with a user different from SYSTEM? What is the "" displayed in 
> the log message "upstreamPipeline... Username: "?
>
> When not using the  Jenkins Authorize Project Plugin 
> , the user used to run the 
> upstream pipelines is SYSTEM as we can see in the sample below
>
> upstreamPipeline (plugins/pipeline-maven-plugin/dependency-graph/my-jar, 
>> visibleByDownstreamBuildAuth: true),  downstreamPipeline 
>> (plugins/pipeline-maven-plugin/dependency-graph/my-war-multibranch/master, 
>> visibleByUpstreamBuildAuth: true), *upstreamBuildAuth*: 
>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>> *Username: 
>> SYSTEM*; Password: [PROTECTED]; Authenticated: false; Details: null; Not 
>> granted any authorities
>
>
> Cyrille
>
>
> On Thursday, August 1, 2019 at 9:26:34 AM UTC+2, drpm wrote:
>>
>> 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 (, visibleByDownstreamBuildAuth: 
>> false),  downstreamPipeline (, 
>> visibleByUpstreamBuildAuth: true), upstreamBuildAuth: 
>> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
>> Username: ; Password: [PROTECTED]; *
>>
>> *Skip triggering of  by  
>> #: 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
>>  
>> *
>>
>> Thank you in advance. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/078cff11-af32-41cc-880b-39c0dd3daf62%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-01 Thread Cyrille Le Clerc

Hello,

Could you be using the Jenkins Authorize Project Plugin 
 and impersonate your builds 
with a user different from SYSTEM? What is the "" displayed in the 
log message "upstreamPipeline... Username: "?

When not using the  Jenkins Authorize Project Plugin 
, the user used to run the 
upstream pipelines is SYSTEM as we can see in the sample below

upstreamPipeline (plugins/pipeline-maven-plugin/dependency-graph/my-jar, 
> visibleByDownstreamBuildAuth: true),  downstreamPipeline 
> (plugins/pipeline-maven-plugin/dependency-graph/my-war-multibranch/master, 
> visibleByUpstreamBuildAuth: true), *upstreamBuildAuth*: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
> *Username: 
> SYSTEM*; Password: [PROTECTED]; Authenticated: false; Details: null; Not 
> granted any authorities


Cyrille


On Thursday, August 1, 2019 at 9:26:34 AM UTC+2, drpm wrote:
>
> 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 (, visibleByDownstreamBuildAuth: false), 
>  downstreamPipeline (, visibleByUpstreamBuildAuth: 
> true), upstreamBuildAuth: 
> org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: 
> Username: ; Password: [PROTECTED]; *
>
> *Skip triggering of  by  #: 
> 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
>  
> *
>
> Thank you in advance. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3844ab1a-5d02-4338-bc3e-46aae255c384%40googlegroups.com.

Jenkins Pipeline Maven Plugin - Always skipping downstream job

2019-08-01 Thread drpm

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 (, visibleByDownstreamBuildAuth: false),
downstreamPipeline (, visibleByUpstreamBuildAuth:
true), upstreamBuildAuth:
org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f:
Username: ; Password: [PROTECTED]; *

*Skip triggering of by #:
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

Thank you in advance.

--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c8371a13-5d3c-4df2-b477-380d823e07be%40googlegroups.com.

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Re: Jenkins Pipeline Maven Plugin - Always skipping downstream job

Jenkins Pipeline Maven Plugin - Always skipping downstream job

12 matches

Site Navigation

Mail list logo

Footer information