Increase granularity of administration

Comments

3 comments

  • Avatar
    Deepthi Chandramouli

    Hi Mark,


    Thanks for your feedback. 


    This request is already in the backlog for our 2.x set of releases. We are planning to implement this functionality in early 2.x, as part of moving the administration from editing the xml configuration file to a graphical interface.


    We will introduce administrators for pipeline groups in addition to the existing view and operate users.


    Deepthi

    0
    Comment actions Permalink
  • Avatar
    Mark Crossfield

    That sounds great. I think it is worth saying however that the pipeline group administrators should only be able to alter the pipeline, not the user roles. We need to be able to allow developers to change their pipeline but not have control over the approval of later stages.


    Once this feature is available we will be able to consider Cruise as an end to end pipeline, deploying into production.


    Many thanks, Mark

    0
    Comment actions Permalink
  • Avatar
    Anush Ramani

    Hi Mark,


    The Group Admin role is now available in the first Go 2.1 early access build.


    We considered your suggestion to restrict group admins to only being able to edit pipelines. However, we decided to give the group admin the ability to also manage permissions within the pipeline group because the more common use case is the need for a project admin (or lead developer who controls access to his project).


    Hope you find the feature useful.


    -Anush

    0
    Comment actions Permalink

Please sign in to leave a comment.