-
LEON ALEKSEYEV
- PowerBuilder
- Monday, 4 May 2020 07:06 PM UTC
Hello. My company is using GIT BitBucket. We are in process of migrating our apps to PowerBuilder 2017 R3 Build 1915 and so far do not have much luck with GIT. We are facing two issues:
(1)
The local repository PB creates, ws_objects, has somewhat odd structure that is challenging to understand.
Let’s say there is a non-visual object called mv_n_tabpage_input_funcs in the PBL named mv_nvo. What we’re seeing upon creation of local repo is the following structure:
The strange thing here is that each PBL is represented with TWO directories - mv_nvo and mv_nvo.pbl.src in this case. The mv_nvo folder, however, also has a subfolder named mv_nvo.pbl.src containing the same set of source files as the "standalone" mv_nvo.pbl.src folder.
The same? It actually was a shocking discovery that files in the two sets are of different versions!
The ones stored in the “inner” mv_nvo/mv_nvo.pbl.src folder are up-to-date, while those in the “standalone” mv_nvo.pbl.src folder are seriously outdated. Some turned out to be approximately a year old.
Is there any explanation to this? How should we proceed? How can we ensure GIT will always have the latest file versions and won’t accidentally overwrite them with the older ones? Should we manually delete the old versions of files elsewhere before pushing to central GIT repo on the server?
(2)
For some odd reason, each app ended up having 1-3 objects (datawindows) that PB failed to add to local repository, giving a generic failure error with no details/explanations. Regenerating these dw's did not help a bit. Eventually I had to manually exclude (uncheck) them from the “add files” list in order to let the process run through. I’m attaching one of such datawindow source files, mv_dw_hsg_issue_desc.srd. Could someone look into it and hopefully tell us why this particular object could not be added to local ws_objects repo?
Thank you very much - we will greatly appreciate any help/clarifications.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.