Entry for Promotion/Promote authorizationMatrix is broken/doesn't work for building from casc
See original GitHub issueYour checklist for this issue
🚨 Please review the Support Policy
- The question was asked in the project’s Gitter chat
- Jenkins version - 2.345-jdk11
- Plugin version - Matrix Authorization Strategy 3.1.2 / Configuration as Code Plugin 1429.v09b_044a_c93de
- OS - Ubuntu
- Reproduction steps
Description
We’re using Matrix Authorization Strategy and configuration-as-code plugin to define an Authorization Matrix. For jobs that use promotion, there is a column in the matrix for Promotion/promote permission.
Therefore, I added to my j2 template the following:
- 'GROUP:Promotion/Promote:dev'
- 'GROUP:Promotion/Promote:jenkins_editor'
- 'GROUP:Promotion/Promote:staff'
However, jenkins wouldn’t build and gave this error:
Failed to parse 'GROUP:Promotion/Promote:dev' --- no such permission
So question, if Promotion/Promote isn’t right, what is? Or does this plugin not handle that permission? What should be my next steps?
Issue Analytics
- State:
- Created a year ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Jenkinsci Configuration-As-Code-Plugin Statistics & Issues
Entry for Promotion/Promote authorizationMatrix is broken/doesn't work for building from casc, closed, 12, 2022-06-20, 2022-09-26, 2022-06-28.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@timja thank you for this! That was it, based on our testing!
Our colleague has a fix PR up if anyone in this thread is able to review: https://github.com/jenkinsci/promoted-builds-plugin/pull/208
Thanks for the contribution, given this isn’t a bug in JCasC I’m going to close this issue at this point.