• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Component/s: role-strategy-plugin
• Labels:

  • gsoc-2019-project-idea
  • plugin
  • role_strategy
  • user-experience
• Environment:

  Jenkins 1.599;
  Role-based Authorization Strategy 2.3.2;
  Windows Server 2008 R2 Standard;
  Chrome,Opera,IE8;
  Java 1.8;

[JENKINS-41594] Role-based Authorization Strategy plugin questions/suggestions

Vlad Oparlescu created issue - 2017-01-31 13:29

Vlad Oparlescu made changes - 2017-01-31 13:29

Epic Link

New: JENKINS-37913 [ 174055 ]

Vlad Oparlescu made changes - 2017-01-31 13:44

Description

Original: Dear all, I installed at the office Jenkins plugin Role-based Authorization Strategy and I have some oncerns/questions reagarding this.It would be helpful to me if you could give me some answers,hints reagarding the content below: *1)* should be a way to edit the pattern of a project. Currently it looks like the only way to change the definition of a project is to delete it and re-create it with a new definition. When doing this, it is possible to lose all the role assignments existing for that project.if you SAVE or APPLY the deletion before SAVE or APPLY of the new definition. This will not be nice for adding new model years, etc to a Project. *2)* it would be nice to equate a view to a project (i.e. define a project X as "all jobs in view X"). Then we could just add/remove jobs in a view, and this would easily update the project definition. Is it possible for the macro feature of this plugin to do that? *3)* it would be nice to be able to evaluate which jobs a Pattern matches before applying the pattern to a role. If my set of jobs/names/regular expression is at all complex, this can be difficult to determine. Many thanks, Vlad

New: Dear all, I installed at the office Jenkins plugin Role-based Authorization Strategy and I have some concerns/questions regarding this.It would be helpful to me if you could give me some answers,hints regarding the content below: *1)* should be a way to edit the pattern of a project. Currently it looks like the only way to change the definition of a project is to delete it and re-create it with a new definition. When doing this, it is possible to lose all the role assignments existing for that project.if you SAVE or APPLY the deletion before SAVE or APPLY of the new definition. This will not be nice for adding new model years, etc to a Project. *2)* it would be nice to equate a view to a project (i.e. define a project X as "all jobs in view X"). Then we could just add/remove jobs in a view, and this would easily update the project definition. Is it possible for the macro feature of this plugin to do that? *3)* it would be nice to be able to evaluate which jobs a Pattern matches before applying the pattern to a role. If my set of jobs/names/regular expression is at all complex, this can be difficult to determine. Many thanks, Vlad

Oleg Nenashev made changes - 2018-12-25 09:33

Labels

Original: jenkins plugin role_strategy

New: gsoc-2019-project-idea plugin role_strategy user-experience

Markus Winter made changes - 2022-12-29 22:59

Released As		New: 575.v4d286a_03e6d7
Assignee	Original: Vlad Oparlescu [ vladoparlescu ]	New: Markus Winter [ mawinter69 ]
Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]