Hello to all. I have a problem with PB2017R2 & Git. Let's put the case: - There is a project in the repositories and 10 programmers are working correctly. - At this point I decide to involve another person (11th) in the project. - I carry out a 'git clone' of the project on the new workstation. (in our configuration we exclude the PBLs from the GIT management including '*.PBL' in the '.gitignore' file) - at this point I copy the *.pbl from one of the programmers to the 11th person. - The next step is to open the pbw and connect it to GIT. Here the problem occurs. PB regenerates all the objects in the library and exports them, overwriting those that came from the 'clone'. In doing so I lost the correct sources ( from clone ) and overwritten them with a previous version ( pbl export ). How can I solve the problem ? It is impossible to align all staff and stop them until I added 11th. Thanks for the reply.
- ATK Gimmy Susan
- PowerBuilder
- Wednesday, 30 May 2018 23:24 PM UTC
- Page :
- 1
There are no replies made for this question yet.
However, you are not allowed to reply to this question.
However, you are not allowed to reply to this question.
ty for your answer.
One question again.
If i have my pbl in sync With The remote repository i have Many conflict ( every sync)
if 2 users modify a different obj in The same library, i have a conflict.
how i resolve tris case?
ty 1k for your patience
Gmy
The PBLs will be rebuild from source code in the ws_objects folder. So you can use a client like TortoiseGit to resolve all the PBL-related conflicts by accepting either the client side or server side PBL.
As to the conflict resulting from modifying different objects in the same PBL, this issue will be fixed in the R3 release, which will be available by the end of July if everything goes well. Currently, please use a Git tool to resolve the conflicts manually.
Regards,
Tom Jiang