Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Pages: 1
I have written scripts to do a Full and Update check out of the source (*.sr?) filesfrom PVCS. I also have written scripts to do either a PowerGen Bootstrap Import (/J) or a Synchronize (/K) of each PB engineers' PBLS based on these *.sr? source files. These scripts are meant to be run by the individual PowerBuilder engineer to update their local PBLs from the latest PVCS checked in source (PowerBuilder 8 is not doing this properly.)
These scripts work well on a Bootstrap but when they do a Synchronize it overwrites the PBLs they are currently working on. What is the process for preventing this from happening? Thanks.
I'm not sure I understand. When you say that the Synchronize "overwrites the PBLs", what do you mean? Can you describe the configuration you're using for the developers? Maybe use an example?
Regards,
Phil
The developer working in PowerBuilder 8 will have one or more objects checked out via Powerbuilder. They will sometimes get the latest version of the code by running my synchronization scripts. The scripts run several commands:
...
REM Update Local Source from PVCS
REM --------------------------------------------------
pcli get -u -pr""V:\CM\Projects\Application Source Code"" -a%SrcDir%/pvcs -o -z -bp/ -pp""/Proj Name"" Base Base2 > %LogFile%
...
REM Syncronize the PBLs
REM --------------------------------------------------
%WorkDir%\pwrgn8 /K=%ProjFile% %ListFile% /L=%LogFile%
...
REM Rebuild all the PBDs
REM --------------------------------------------------
%WorkDir%\pwrgn8 /P=%ProjFile% /L=%LogFile2%
...
At this point the engineers claim the local code they were working on no longer has the changes they had made but not checked back in to PVCS. Is it possible to synchronize the PBLs with the latest PVCS source and not overwrite checked out code? Thanks.
There is a PowerGen option to exclude updating objects based on the file attributes of the source files. Many source control systems change the attributes of the checked out files. Can you use this option to achieve what you're trying?
Regards,
Phil
Hi Phil
Our team here are also having this problem with Powerbuilder 8 and PowerGen. A while back we had some email correspondance and came to the same conclusion, but we have found we still have intermittant problems.
When checking out of Visual Source Safe, we have it changes the sr? file to Read-Write, which meant that we could ignore files with that attribute when importing/synchronising. Unfortunatly we have found the VSS is tempermental and does not always change the file status.
We have looked into many different methods of making sure that the files go read-write, but without writing anything specialised we haven't been able to get it working.
Would it be possible to get an option in PowerGen that will check whether the object has been checked out (I notice that PBLExplorer is able to see that status) and not import based on that?
Cheers,
Jarom
Jarom,
PBLExplorer uses the "metadata" stored in the PBL that indicates which objects are checked out. With PB8 this metadata was eliminated. After PB8 the only way to determine which objects are checked out is to either query the source control system directly or use some attribute of the checked out file.
To date we have chosen not to create an interface directly to the SCS. The interfaces tend to be indiosyncratic (even through the "standard" SCC-API) and difficult to support.
In addition to the read/write attributes of the files that PowerGen currently uses, we are implementing options to compare the modification dates of the object in the PBL with the modification dates of the checked out files, and to use that comparison to exclude objects from being imported. These options will be available shortly and may prove to be more reliable for VSS then read/write attributes that you have tried. We'll announce this when it's ready; probably in the next couple weeks.
Regards,
Phil
Pages: 1