[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Daniel Beck commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy Yes, with Authorize Project/Matrix Auth. Something like https://plugins.jenkins.io/job-restrictions probably does that though. If you need further assistance, I recommend you ask on the Jenkins Users mailing list. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7819.1574869860518%40Atlassian.JIRA.
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Michel Zanini commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy Thanks for the replies, I will close the issue. Just a final question: If have a user, lets say michel and two jobs, jobA and jobB, it does not seem to be possible to authorise the user to run jobA on a node and NOT allow jobB to run on that same node for that same user? It's either both or none, correct? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7782.1574866080275%40Atlassian.JIRA.
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Daniel Beck closed an issue as Not A Defect The described behavior is as designed. Jenkins / JENKINS-60300 Inheritance issues with Project-based matrix strategy Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https:/
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Daniel Beck commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy It's available for individual agents too – in their configuration. This is how you prevent your evil, untrustworthy users from building on the master node Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7755.1574864040151%40Atlassian.JIRA.
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Michel Zanini commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy Ok I see. So I guess the fact that Agent/Build is only available at the top Global level, I can't change it locally at job level to block it, correct ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7752.1574863980205%40Atlassian.JIRA.
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Daniel Beck commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy on the node. Specifically the master node, whose name is "Jenkins", which could be confusing. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7750.1574863740169%40Atlassian.JIRA.
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Daniel Beck commented on JENKINS-60300 Re: Inheritance issues with Project-based matrix strategy See Screen Shot 2019-11-27 at 09.23.52.png Read the error message carefully: It doesn't stop you from building the project, just from building on the node. Job/Build is required to trigger the build, this is done by admin here (or whoever uses the UI). While in the queue, the build takes on the identity of the configured Authorize Project user michel, and checks Agent/Build to see where it can run. Would that explain it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203295.1574858547000.7743.1574863203076%40Atlassian.JIRA.
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Michel Zanini updated an issue Jenkins / JENKINS-60300 Inheritance issues with Project-based matrix strategy Change By: Michel Zanini Hi,I am testing the usage of Project-based matrix using permissions inheritance. The result of the testing is not matching the expected behaviour, I am unaware if it's a bug or something I am missing.This are the steps I did and what happened vs what I expected:1. On Manage Jenkins -> Configure Global Security I setup Project-based Matrix Authorization Strategy and Access Control for Builds with the Authorise Project plugin as following:See _Screen Shot 2019-11-27 at 09.23.09.png_ (users _michel_ and _zanini_ have only read permissions). See _Screen Shot 2019-11-27 at 09.23.25.png_ (I have configured to run all builds with the user _michel_).2. I created a test project on root of Jenkins. When I run it, I get a build blocked as there is no permissions for user _michel_, and that works as expected. See _Screen Shot 2019-11-27 at 09.23.52.png_.3. Now I open the test project and enable project based security for it. Then I change to use the inheritance strategy to not import global permissions and select that the user _michel_ has ALL permissions for this job. See _Screen Shot 2019-11-27 at 09.24.14.png_.*When I run the job, I would expect _michel_ to be able to run it, as I specified that this user can do everything with the job locally at the job level. But what happens is the same as before, user can't build the job.* 4. I then make changes to ** global permissions to add build permission for both users, like in _Screen Shot 2019-11-27 at 09.37.33.png_. Now the job can build like in _Screen Shot 2019-11-27 at 09.38.41.png_. 5. I then configure for this job to run as _zanini_ user like in _Screen Shot 2019-11-27 at 09.39.24.png._ *Now I would expect the job not NOT to run and be blocked, because I configured the job to block global inheritance, and locally is only configured only for _michel_. But the job runs with the user fully .* It seems that only global permissions are being looked at and local job permissions are not.Is this correct? What I am missing here? Thanks. Add Comment
[JIRA] (JENKINS-60300) Inheritance issues with Project-based matrix strategy
Title: Message Title Michel Zanini created an issue Jenkins / JENKINS-60300 Inheritance issues with Project-based matrix strategy Issue Type: Bug Assignee: Daniel Beck Attachments: Screen Shot 2019-11-27 at 09.23.09.png, Screen Shot 2019-11-27 at 09.23.25.png, Screen Shot 2019-11-27 at 09.23.52.png, Screen Shot 2019-11-27 at 09.24.14.png, Screen Shot 2019-11-27 at 09.37.33.png, Screen Shot 2019-11-27 at 09.38.41.png, Screen Shot 2019-11-27 at 09.39.24.png Components: matrix-auth-plugin Created: 2019-11-27 12:42 Environment: Jenkins 2.206 Matrix Authorization Strategy Plugin 2.5 Priority: Minor Reporter: Michel Zanini Hi, I am testing the usage of Project-based matrix using permissions inheritance. The result of the testing is not matching the expected behaviour, I am unaware if it's a bug or something I am missing. This are the steps I did and what happened vs what I expected: 1. On Manage Jenkins -> Configure Global Security I setup Project-based Matrix Authorization Strategy and Access Control for Builds with the Authorise Project plugin as following: See Screen Shot 2019-11-27 at 09.23.09.png (users michel and zanini have only read permissions). See Screen Shot 2019-11-27 at 09.23.25.png (I have configured to run all builds with the user michel). 2. I created a test project on root of Jenkins. When I run it, I get a build blocked as there is no permissions for user michel, and that works as expected. See Screen Shot 2019-11-27 at 09.23.52.png. 3. Now I open the test project and enable project based security for it. Then I change to use the inheritance strateg
