Jump to content
Misieq

replicatewrite permission for sub-branches

Recommended Posts

Hi

I have following problem. It looks that replicatewrite permission is always propagating from parent branch.

I have following use-case:

/development branch for which I want to gran ci and replicatewrite permission only for Build Manager

/development/taskXXX task branches which are created by developer

Normally when developer starts working on the task following actions are taken:

1) pull /development into local repo

2) create task sub-branch in local repo

3) push task sub-branch into cetral

If I do not grant permission replicatewrite for /development branch than replication proces of sub-branch fails.

What shall be permission setting for such use-case?

Thanks in advance.

Share this post


Link to post
Share on other sites

Hello,

 

can you tell me if the denied replicatewrite permission is denied at the "repository"/"repository server" level?

 

The thing is the branches, it doesn't matter if they are child or not, they all inherit from the repository and repository server objects, not from their parent branches.

 

The command output of the following commands will be very useful:

cm showacl br:/development/taskXXX
cm showacl br:/development/taskXXX --extended

Can you execute them and post us the results?

 

Thanks

Share this post


Link to post
Share on other sites

I can run this comment only on local (developer's) server - on central server branch does not exist yet.

It looks that it has all rights granted.

ACL: 0

User Permission Allowed Denied InheritedFrom

ALL USERS all Yes repserver:localserver:8087

ACL: 0

Creator rep:repository@repserver:localserver:8087

Inherited

ACL: 0

Creator repserver:localserver:8087

Entries

ALL USERS:

Allowed:

all

Please note that:

Problem appears when replicating branch which do not exists on remote server (it will be created there as a result of replication).

Local server work in UPMode, central one work with LDAP and replication is run with proper profile.

Share this post


Link to post
Share on other sites

Thanks for remarking the last detail,

 

I'm able to reproduce it and it's indeed a bug, we are going to fix it asap.

 

The permissions are wrongly checked for the parent branch.

Share this post


Link to post
Share on other sites

Hello

Is this issue already solved?

If yes please provide me information in which version.

If not what is your plan for it :)

Thanks in advance.

Share this post


Link to post
Share on other sites

Hello

 

Could you please tell me if this issue has been fixed already?

I haven't seen anything about it in release notes so far.

 

Regards

Share this post


Link to post
Share on other sites

I'm sorry i'ts not started yet.

 

It's in our pending-to-fix list so we didn't forget about it.

Share this post


Link to post
Share on other sites

Dear codice staff,

 

I'm afraid that I have faced exactly the same problem as the reporter which is a show stopper for my small team of developers who work in a distributed way. It is super sad to see this issue has not been fixed yet after 9 MONTHS of being reported! Unacceptable from my point of view since this is a VERY common operation that distributed teams do.

 

I'm sorry but this is very discouraging now that I just bought two additional annual licenses for the team. Is there a workaround? When is this going to be fixed? I'm a paid customer, let me know if you need my details.

 

Please help.

 

Regards,

Gus

Share this post


Link to post
Share on other sites

Hello Gus,

 

I've just updated the task with your information and upgraded the priority to the max.

 

Let's see if we can have it for the next sprint.

Share this post


Link to post
Share on other sites

Hello

It's far more than year since problem was signaled.

Is there any progres with fix implementation? When could it be expected?

Issue affects a lot permissions setting in my environment.

Share this post


Link to post
Share on other sites

Hello Misiew,

I'm truly sorry, I promise you it's in our top 5 issues reported by customers to be fixed.

We are completely swamped in new features and we are trying to do our best to satisfy everyone, but I'm sorry this hasn't been fixed yet.

Share this post


Link to post
Share on other sites

Hello

I know that you are focused on 6.0 branch right now, but any progress with this issue?

It was reported year and the half ago.

Share this post


Link to post
Share on other sites

I'm sorry Misieq, the issue remains in the same status. I'll try to push it once again.

Sorry for the long waiting :(

Share this post


Link to post
Share on other sites

@Misieq we have a new year's present for you!

The task has already implemented and it's under the revision/validation/testing pipeline!

Thank you for your patience...

 

Share this post


Link to post
Share on other sites

Hello Manu,

I am having the same exact issue, I am using the latest Version 6.0.16.1765

BTW is this issue exist in the upcoming version 7 ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×