-
Jason Schultz
- PowerBuilder
- Wednesday, 17 March 2021 06:26 PM UTC
Hello,
I have a question about the behavior we're seeing between our PB environment and SVN.
Background Info:
- Our source code repository used to be managed via PVCS, we've since migrated to SVN.
- After migrating to SVN, each developer on our team initially 'Connected to Workspace' via PB IDE (pointing to our SVN server), creating a local repository of all objects as well as a ws_objects folder in our local repository.
- On the SVN server side, we also have a ws_objects folder. We use TortoiseSVN Repository Browser as our GUI utility.
- Since integrating PB with SVN, we've successfully been able to make a change, perform SVN Commit and have other developers do an SVN Update with no issue. Green dots beside all objects, etc.
Observed Behavior:
A co-worker recently made a change to an object (in this case, a DataWindow object .srd).
After performing an SVN Commit, they noticed the following:
a) All green dots next to objects in PB IDE (as expected). Opening DataWindow object within PB IDE displays expected result (contains latest change)
b) Toggling over to File Explorer and navigating to the corresponding object (.srd file) that the PB Workspace/IDE refers to, the date/timestamp is older and viewing the object syntax in Notepad still shows previous object code.
c) Still within File Explorer, drill down into the local repository WS_Objects folder / PBL.SRC / DataWindow object .srd file, it contains the latest datetimestamp and source code contents (same as (a)).
d) Within TortoiseSVN Repository Browser utility, navigate to the corresponding .srd object, the date/timestamp is older and viewing the object syntax in Notepad still shows previous code (same as (b)).
e) Within TortoiseSVN Repository Browser utility, looking into the ws_objects folder / PBL.SRC / DataWindow object .srd, it contains the latest datetimestamp and source code contents (consistent with (a) and (c)).
After the successful SVN Update, they also performed a full rebuild and deploy. The resulting executable did not contain the latest code enhancement. This is what prompted to examine the above elements, notice the above discrepancy between the various objects, and try to identify where the disconnect may be.
f) A 2nd developer performed an SVN Update and successfully retrieved the changed .srw, but same results as above (points (a) thru (e)).
Expected Results:
- We thought we had a proper understanding of how we needed to integrate PB with SVN, and the purpose/concept of the ws_objects folder. Given the above observations, this may not be the case. The ws_objects folder appears to act like a holding place for local repository changes (basically a carbon-copy of what is reflected in the PB IDE). When an SVN Commit occurs, those changed objects in the local repository ws_objects get pushed to the main SVN Repository. This appears to be happening (between the local repository ws_objects and the main SVN repository ws_objects). The thing that is confusing is why we don't see the same latest/greatest change in the PB objects behind the PB GUI and within main SVN repository (b) and (d) above. Are we doing something wrong? I would think after a successful SVN Commit, all would be in sync, and you would see the same thing across the board. We have green dots beside all and have repeatedly tried to do an SVN Update but it acts like all is up to date and in sync. Looking for any assistance / explanation of why we see the above behavior.
I appreciate any feedback and look forward to hearing from anyone with any insight on this topic.
Thanks,
Jason Schultz
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.