|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Hi Martin,
Thanks for your reply.
To reproduce the reported issue, all you need is:
1. Install the Role Strategy Plugin
2. Install the Inheritance Plugin
3. Create Abstract inheritance project, lets call it projA, with parameter paramA, over-writable.
4. Create Inheritance project, lets call it project_final, that extends projA and overwrite inheritance parameter reference paramA.
5. Make sure user TEST_USER has no build privileges in Manage Roles, then create a Project Role with pattern project_.* and enable the job build permissions.
6. assign that role to TEST_USER via the assign roles page.
7. sign in as TEST_USER and you will see the build with parameters button in p which when you click you get user TEST_USER has no job/build permissions.
Even when I set the pattern in step 5 to .* ie everything, I still get the same error, as initially I thought that someone building project_final would require build rights for projA (sounded more like a bug rather than anything else but still)
I will try and have a look in the code to see what is happening.
Alex