CODEWITHSUNDEEP
jenkinsjenkins-pluginsjenkins-pipelinedevops
Gois
Gois

Reputation: 98

Jenkins role strategy plugin and multibranch pipeline

We have two types of projects, a free-style and a multibranch pipeline. I want to have a developer role to get only read access to the jobs, to analyse pipeline log and archived artifacts. For the free-style project works great, but for multibranch, a user within developer role can't see anything, appears the message 'This folder is empty` and triggered builds doesn't appears. Can someone give a light please?

Some screen shots with the configuration: Global roles Project roles

Upvotes: 4

Views: 2300

Answers (2)

Sysanin
Sysanin

Reputation: 1795

I had the same issue, found not perfect solution, but it is works.

One requirement: branch naming in GIT should be persistent, with additional prefix. For example: feat/branchName. Then you can filter it out by this prefix value. see more for branch naming in git flow

As input parameters you have projects and multibranch pipelines inside it. For example:

  • Product1 -> Multibranch_pipeline_Product1 -> different branches with prefixes feat, bug, infra, etc.. (for example: infra/PRJ-135-reciepts-issues, feat/PRJ-337-new-customer, etc)

  • Product2 -> Multibranch_pipeline_Product2 -> different branches with prefixes feat, bug, infra, etc.. (for example: infra/PRJ-876-new-env, feat/PRJ-999-entity-creation, etc)

and you would like to separate it for different users:

  • Developer1 - access only Project1 and branches inside multibranch pipeline
  • Developer2 - access only Project2 and branches inside multibranch pipeline
  • Developer3 - access to Project1 and Project2 multibranch pipelines

So you need the following configuration in you role-based plugin:

Project Roles:

  • Product1 pattern - ^Product1*|.*_Product1*|(.*)feat(.*)|(.*)bug(.*)|(.*)hotfix(.*)|(.*)infra(.*)|(.*)develop(.*)

  • Product2 pattern - ^Product2*|.*_Product2*|(.*)feat(.*)|(.*)bug(.*)|(.*)hotfix(.*)|(.*)infra(.*)|(.*)develop(.*)

where:

  • ^Product1* - will give access to the folder Product1
  • .*_Product1* - will give access to the folder (multibranch project) - Multibranch_pipeline_Product2
  • (.*)feat(.*)|(.*)bug(.*)|(.*)hotfix(.*)|(.*)infra(.*)|(.*)develop(.*) - will give access to the all branches with prefixes feat OR bug OR hotfix OR infra OR develop inside this multibranch project.

And the same you should do for the Product2.

In sum you should have: - Developer1 has role Product1 - Developer2 has role Product2 - Developer3 has both roles, Product1 and Product2

I tested this solution and with such configuration permissions do not intersect (Developer1 will not have access to branches in Product2 and Developer2 will not have access to branches in Product1)

Upvotes: 3

dalmo.santos
dalmo.santos

Reputation: 79

What you can do create 2 distinct jobs, with a single Jenkinsfile, where the branch 'develop' perform specific tasks (sonarqube, unit tests, etc). The 'release' branch performs integration tasks.

Example:

stage 'Init'
node {
   checkout scm
   sh 'echo $ BRANCH_NAME'
}
if (env.BRANCH_NAME == 'develop') {
   stage 'Only on develop'
   println 'This happens only on develop'
} else {
   stage 'Other branches'
   println "Current branch $ {env.BRANCH_NAME}"
}

Look at this link as a reference

Upvotes: -1

Related Questions