[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title Jose A. Iñigo edited a comment on JENKINS-43912 Re: Multibranch pipelines should support role restrictions [~venosov] 's answer solves the problem. Anyway I would suggest an update in the documentation since this is a usual use case and sorting it out is not straightforward. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title Jose A. Iñigo commented on JENKINS-43912 Re: Multibranch pipelines should support role restrictions Víctor Martín Molina solves the problem. Anyway I would suggest an update in the documentation since this is a usual use case and sorting it out is not straightforward. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title
Jose A. Iñigo edited a comment on JENKINS-43912
Re: Multibranch pipelines should support role restrictions
I'd like to give some more context to this problem: The origin of my pipelines is the branch source plugin which creates a structure with a parent folder of my Bitbucket organization and one subfolder per repository, each containing a pipeline per branch with a Jenkinsfile. Thus the Jenkins folder hierachy is as follows:{code:java}Organization |-Repo1 |---master |---develop |-Repo2 |---master |---develop |-Poc-Repo1 |---master |---develop |-Poc-Repo2 |---master |---develop {code}I need to setup permissions so that some users can ONLY see and build repos with the pattern Organization/Poc-.*Other users can see any repoOther can see and build any repo \{{}} The problem is the regexp Organization/Poc-*. doesn't work. Users with this role can't see anything
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title
Jose A. Iñigo edited a comment on JENKINS-43912
Re: Multibranch pipelines should support role restrictions
I'd like to give some more context to this problem: The origin of my pipelines is the branch source plugin which creates a structure with a parent folder of my Bitbucket organization and one subfolder per repository, each containing a pipeline per branch with a Jenkinsfile. Thus the Jenkins folder hierachy is as follows:{code:java}Organization |-Repo1 |---master |---develop |-Repo2 |---master |---develop |-Poc-Repo1 |---master |---develop |-Poc-Repo2 |---master |---develop {code}I need to setup permissions so that some users can ONLY see and build repos with the pattern Organization/Poc-.*Other users can see any repo Other Others can see and build any repoThe problem is the regexp Organization/Poc-*. doesn't work. Users with this role can't see anything
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title
Jose A. Iñigo edited a comment on JENKINS-43912
Re: Multibranch pipelines should support role restrictions
I'd like to give some more context to this problem: The origin of my pipelines is the branch source plugin which creates a structure with a parent folder of my Bitbucket organization and one subfolder per repository, each containing a pipeline per branch with a Jenkinsfile. Thus the Jenkins folder hierachy is as follows:{code:java}Organization |-Repo1 |---master |---develop |-Repo2 |---master |---develop |-Poc-Repo1 |---master |---develop |-Poc-Repo2 |---master |---develop {code}I need to setup permissions so that some users can ONLY see and build repos with the pattern Organization/Poc-.*Other users can see any repoOther can see and build any repo\{{}} * The problem is the regexp Organization/Poc- . * . doesn't work. Users with this role can't see anything *.\{{}}{{}}{{}}{{}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title
Jose A. Iñigo edited a comment on JENKINS-43912
Re: Multibranch pipelines should support role restrictions
I'd like to give some more context to this problem: The origin of my pipelines is the branch source plugin which creates a structure with a parent folder of my Bitbucket organization and one subfolder per repository, each containing a pipeline per branch with a Jenkinsfile. Thus the Jenkins folder hierachy is as follows: { {Organization code:java } }{{}} Organization |- {{ Repo1 }} {{ |---master }}{{ }}{{ |---develop }}{{ |-Repo2 }}{{ }}{{ |---master }}{{ }}{{ |---develop }}{{ }}{{ |- }}{{ Poc- repo1 }} Repo1 {{ }}{{ |---master }} {{ }}{{ |---develop }}{{ }}{{ |- }}{{ Poc- repo2 }} Repo2 {{ }}{{ |---master }} {{ }}{{ | — -- - develop }} { { code } } I need to setup permissions so that some users can ONLY see and build repos with the pattern Organization/Poc-.*Other users can see any repoOther can see and build any repo \ {{}}*The problem is the regexp Organization/Poc-.* doesn't work. Users with this role can't see anything*. \ {{}}{{}}{{}}{{}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43912) Multibranch pipelines should support role restrictions
Title: Message Title
Jose A. Iñigo commented on JENKINS-43912
Re: Multibranch pipelines should support role restrictions
I'd like to give some more context to this problem: The origin of my pipelines is the branch source plugin which creates a structure with a parent folder of my Bitbucket organization and one subfolder per repository, each containing a pipeline per branch with a Jenkinsfile. Thus the Jenkins folder hierachy is as follows: Organization {{}} |-{{Repo1 }} {{|---master }} {{ }}{{|---develop }} |-Repo2 {{ }}{{|---master }} {{ }}{{|---develop }} {{ }} |-{{Poc-repo1 }} {{ }}{{|---master }} {{ }}{{|---develop }} {{ }} |-{{Poc-repo2 }} {{ }}{{|---master }} {{ }}{{|—--develop }} {{}} I need to setup permissions so that some users can ONLY see and build repos with the pattern Organization/Poc-.* Other users can see any repo Other can see and build any repo{{}} The problem is the regexp Organization/Poc-. doesn't work. Users with this role can't see anything*.{{}} {{}} {{}} {{}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41731) Allow the access to the current user's role(s) in the Jenkins 2 pipeline
Title: Message Title Jose A. Iñigo updated an issue Jenkins / JENKINS-41731 Allow the access to the current user's role(s) in the Jenkins 2 pipeline Change By: Jose A. Iñigo It would be great to be able to access the current user's assigned role(s) in the Jenkins 2 pipelines.This would come in handy to determine wether whether the current user is allowed to execute some steps/stages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41731) Allow the access to the current user's role(s) in the Jenkins 2 pipeline
Title: Message Title Jose A. Iñigo updated an issue Jenkins / JENKINS-41731 Allow the access to the current user's role(s) in the Jenkins 2 pipeline Change By: Jose A. Iñigo Summary: Allow the access of to the current user's role(s) in the Jenkins 2 pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41731) Allow the access of the current user's role(s) in the Jenkins 2 pipeline
Title: Message Title Jose A. Iñigo updated an issue Jenkins / JENKINS-41731 Allow the access of the current user's role(s) in the Jenkins 2 pipeline Change By: Jose A. Iñigo It would be great to be able to access the current user's assigned role(s) in the Jenkins 2 pipelines.This would come in handy to determine wether the current user is allowed do to execute some steps/stages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41731) Allow the access of the current user's role(s) in the Jenkins 2 pipeline
Title: Message Title Jose A. Iñigo created an issue Jenkins / JENKINS-41731 Allow the access of the current user's role(s) in the Jenkins 2 pipeline Issue Type: New Feature Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2017/Feb/05 6:34 PM Priority: Major Reporter: Jose A. Iñigo It would be great to be able to access the current user's assigned role(s) in the Jenkins 2 pipelines. This would come in handy to determine wether the current user is allowed do execute some steps/stages. Add Comment
