[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

2018-02-27 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It's not really clear what this is about.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42201  
 
 
  Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

2017-03-11 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-42201  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
 Setting the next build number is a configuration action, so half of the description does not make a lot of sense to me.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

2017-02-27 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42201  
 
 
  Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
 Authorization of job execution and that of CLI is completely unrelated. Removed authorize-project from component/s.  
 

  
 
 
 
 

 
Change By: 
 ikedam  
 
 
Component/s: 
 authorize-project-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

2017-02-20 Thread sqa.valentinma...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Marin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42201  
 
 
  Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
Change By: 
 Valentin Marin  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

2017-02-20 Thread sqa.valentinma...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Marin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42201  
 
 
  Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
Change By: 
 Valentin Marin  
 
 
Labels: 
 plugin security  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

2017-02-20 Thread sqa.valentinma...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Marin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42201  
 
 
  Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Alexander Komarov  
 
 
Components: 
 authorize-project-plugin, next-build-number-plugin, security  
 
 
Created: 
 2017/Feb/20 3:37 PM  
 
 
Environment: 
 Jenkins core: 2.32.1  Next Build Number plugin: 1.4  Authorize Project: 1.3.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Valentin Marin  
 

  
 
 
 
 

 
 We got AD authentication enabled on all of our Jenkins servers and have limited the ability to launch and configure jobs to only logged-in domain users. Anon has only read, extended read and workspace job-related permissions. Running set-net-build-number via shell with authorization strategy for that job set as 'Run as User who triggered build' produces permission denied-type error: 00:00:00.059 + java -Djavax.net.ssl.trustStore=jenkinsserver.domain.com -Djavax.net.ssl.trustStorePassword=StorePass -jar jenkins-cli.jar -s https://jenkinsserver.domain.com/ set-next-build-number Job_Name 10 00:00:01.975  00:00:01.979 ERROR: anonymous is missing the Job/Configure permission Also, when I enable 'Block inheritance of global authorization matrix' and explicitly set Anonymous permissions to allow for job configuration, the issue still persists and the same error appears. Command executes successfully only after setting job/configure permission on a global level.