I checked the ws_objects src object and changes are there.  I deleted all the pbds in the pb_src folder.  I download the exe and pbd and my changes are not there.  They are dated with the build date time.  

Any suggestions.

Thanks

Glenn Benscoter

I am using PowerBuider 2017 R3, GITLab (Self- Managed) on Linux with a Windows Runner.  I have established a pipeline.  It runs when I commit and push from PB.  The pipeline passes and I download the exe and pbds.  BUT my changes are not there.  Changes are in the pbl.src folders.  

What am I missing.

start session

set debug true

;********************************************************************************
;* set localprojpath to the parent folder of ws_objects *
;********************************************************************************
scc set connect property localprojpath ".\SAIL_PB_Src\"
;********************************************************************************
;********************************************************************************
scc connect offline
;********************************************************************************
;* set name and location of target for the build and refresh_all *
;********************************************************************************
scc set target ".\MBDA01.pbt" "refresh_all importonly"
;********************************************************************************
;* do a complete refresh of the target pbls *
;********************************************************************************
scc refresh target 3pass
;********************************************************************************
;* build the pbds for the liblist *
;********************************************************************************
build library ".\MBDA01.pbl" "" pbd
;********************************************************************************
;* set any words to go with properties of exe *
;********************************************************************************
set exeinfo property productversion "7.05 GIT Bld 1"
;*******************************************************************************
;* build executable *
;*******************************************************************************
build executable ".\MBDA01.exe" "..\Bitmaps_and_Icons\MBDA01.ico" "" "yy"
*******************************************************************************

scc close

end session

Hi Dana,

This is information I had sent you since about PowerGen and PBGs (they don't exist with Git/SVN integration) with PB2017 R3.  But information for others...

Thank you Danial - we'll investigate your suggestions - and yes an article outling this type of integration would be fantastic!

Hi Dana,

hope my experiance helps... I have done a migration to GIT with Azure DevOps and I'm using the Appeon Autocompile feature (Orca script and pbc170.exe)

So PowerBuilder with Git requires that you add the PBL files only once. And for your project it is necessary that the PBL files are seperated in different subfolders(I will explain this in detail in a second). Now when you add your project to GIT, Powerbuilder will create a ws_objects folder at level of the Workspace file. 

Now I come to the server/CI part. On the server you can write an Orca script file to refresh the PBL from the source Code (here an example https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/175-continuous-integration-with-powerbuilder-2017-bonobo-git-and-jenkins). And this is the point where it is necessary that all PBL file is in a seperate folder, because the Orca script will copy all the source code files (under the path of the pbl in the ws_objects folder) to the actual PBL and generate an PBG.

So

Do we have to copy all the source files in the ws-objects to the actual folders referenced in the pbt files?

- now the Orca script exe do it for you

Do we have to upload the PBls?

- yes, but only once. If you upload it again it will result in merge conflicts

How is does GIT build now with now without the .pbg(s)?

- Orca Script do it for you, after all files under the ws_object path are copied on the same level where the pbl is located

Basically the issue is that comitted and pushed changes and not being built into the exe.....help? 

- you need an orca script file that refresh the pbl files with the actual source code like 

start session
set debug true  
scc set connect property logfile "createpbls.log"  
scc connect offline   
scc set target "pfc_ci\pfc_ci.pbt" importonly  
scc exclude liblist "pbdom\pbdom170.pbd"   
scc refresh target 3pass  
scc close   
end session  

Hope this helps you !!!

Finding out how this works costs me 2 weeks. All the documentation is not on a level which a developer need...thats a pain/shame...sry...

GIT won't create the PBL files, how are you doing that?

We use TFS and PowerGen runs in batch mode at night. Then in the morning I run a .bat file to copy the fresh PBL files to my laptop.

If you don't get a better answer, you could connect your workspace to PBNative and do an Add to Source Control. Now you will have all the .sr* files and .pbg files in a folder structure that matches the folder structure of your target.

You can then do your PowerGen bootstrap build from there.