Misieq Posted September 29, 2015 Report Share Posted September 29, 2015 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. Link to comment Share on other sites More sharing options...
manu Posted September 29, 2015 Report Share Posted September 29, 2015 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 Link to comment Share on other sites More sharing options...
Misieq Posted September 30, 2015 Author Report Share Posted September 30, 2015 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. Link to comment Share on other sites More sharing options...
manu Posted September 30, 2015 Report Share Posted September 30, 2015 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. Link to comment Share on other sites More sharing options...
Misieq Posted September 30, 2015 Author Report Share Posted September 30, 2015 Could you please tell me if fix is required on server side or it will be enough to update client in the future? Thanks in advance. Link to comment Share on other sites More sharing options...
manu Posted September 30, 2015 Report Share Posted September 30, 2015 This will be a server-side fix. Link to comment Share on other sites More sharing options...
Misieq Posted December 2, 2015 Author Report Share Posted December 2, 2015 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. Link to comment Share on other sites More sharing options...
Misieq Posted December 17, 2015 Author Report Share Posted December 17, 2015 Just to remind... Any progress on this topic? Link to comment Share on other sites More sharing options...
calbzam Posted December 21, 2015 Report Share Posted December 21, 2015 Hi, Sorry, I´m afraid that the task hasn´t been performed yet. Regards, Carlos. Link to comment Share on other sites More sharing options...
Misieq Posted June 8, 2016 Author Report Share Posted June 8, 2016 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 Link to comment Share on other sites More sharing options...
manu Posted June 9, 2016 Report Share Posted June 9, 2016 I'm sorry i'ts not started yet. It's in our pending-to-fix list so we didn't forget about it. Link to comment Share on other sites More sharing options...
gusdpr Posted July 5, 2016 Report Share Posted July 5, 2016 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 Link to comment Share on other sites More sharing options...
manu Posted July 5, 2016 Report Share Posted July 5, 2016 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. Link to comment Share on other sites More sharing options...
Misieq Posted October 7, 2016 Author Report Share Posted October 7, 2016 Hello Is there any progress on this point? In release notes nothing is mentioned. Link to comment Share on other sites More sharing options...
Misieq Posted October 24, 2016 Author Report Share Posted October 24, 2016 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. Link to comment Share on other sites More sharing options...
manu Posted October 25, 2016 Report Share Posted October 25, 2016 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. Link to comment Share on other sites More sharing options...
Misieq Posted December 16, 2016 Author Report Share Posted December 16, 2016 Hi manu It's just to remind you that I am here and still waiting. Will Codice make me a present for Christmas? Regards Link to comment Share on other sites More sharing options...
Misieq Posted March 3, 2017 Author Report Share Posted March 3, 2017 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. Link to comment Share on other sites More sharing options...
manu Posted March 6, 2017 Report Share Posted March 6, 2017 I'm sorry Misieq, the issue remains in the same status. I'll try to push it once again. Sorry for the long waiting Link to comment Share on other sites More sharing options...
Misieq Posted August 17, 2017 Author Report Share Posted August 17, 2017 Hello Manu Any progress in this area? It will be nearly two years since reporting - it starts to not look good Link to comment Share on other sites More sharing options...
manu Posted August 18, 2017 Report Share Posted August 18, 2017 It's still in our list and we try to push it to the pipeline, no luck so far. Sorry. Link to comment Share on other sites More sharing options...
manu Posted January 8, 2018 Report Share Posted January 8, 2018 @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... Link to comment Share on other sites More sharing options...
Misieq Posted January 8, 2018 Author Report Share Posted January 8, 2018 Perfect. Looking forward to see it released. Thank you. Link to comment Share on other sites More sharing options...
manu Posted January 9, 2018 Report Share Posted January 9, 2018 Keep tuned, I think it's going to be ready in few days Link to comment Share on other sites More sharing options...
Khaled Posted February 16, 2018 Report Share Posted February 16, 2018 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 ? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.