Same issue here. Even if we explicitly grant the user the job/configure permission they are still unable to make changes on the repository configuration page. This is wildly annoying as our current configuration requires us to poll for new branches that are created and the default polling period is one day. Is there a version of the plugin this works with that we can roll back to or is it due to updates in newer versions of jenkins? We are running:
In my organization we are running into the same issue but we are using "Role-Based Strategy" instead of "Logged-in users can do anything". The users are LDAP users. (MS Active Directory)
The message in the log is the same as the one posted by the Reporter.
In my organization we are running into the same issue but we are using "Role-Based Strategy" instead of "Logged-in users can do anything". The users are LDAP users.
The message in the log is the same as the one posted by the Reporter.
Agreed. Another release of the module and still this problem exists. Setting this issue as a blocker so hopefully, it gets picked up before the next release. There is no workaround that I know of to get the module to operate properly.
Bitbucket Team is creating jobs based on the Jenkinsfile in each branch. It kinda makes sense that Bitbucket Team doesn't have configure permission to change the Jenkinsfile dynamically.
The error message is confusing but the issue shouldn't be a blocker. You just have to make change to the Jenkinsfile instead of changing the configuration from the UI.
We have just encountered this - using Role based permissions and a Bitbucket Folder project. Is the suggestion that the bit where permission denied is shown can only be adjusted through the Jenkinsfile? I.e. it's really the wrong error message?
For the comments regaurding having to setup permision in the jenkinsfile, That only sets the permisions on the branch plans, The multibranch pipelines that get created by the plugin don't inherit the permisions of the child based on the jenkinsfile. The default should be to always inherit from the parent.
For the comments regaurding regarding having to setup permision permission in the jenkinsfile, That only sets the permisions permissions on the branch plans, The multibranch multi branch pipelines that get created by the plugin don't inherit the permisions permissions of the child based on the jenkinsfile. The default should be to always inherit from the parent.