1. Jan Hoppe
  2. PowerBuilder
  3. Tuesday, 7 January 2020 09:26 AM UTC

The "stand alone compiler" option seems very nice, but we need to get the PBL's updated from TFS as well, does anybody know if an automated "Get Latest" or similar is also possible?

Jan Hoppe Accepted Answer Pending Moderation
  1. Wednesday, 8 January 2020 07:39 AM UTC
  2. PowerBuilder
  3. # 1

Thank you for your responses.

Rene, as I read it, it is the Jenkins that will do the "Get latest" for me, is that correct?

and Michael you believe that I can do the "Get latest" using orcascript, correct?

 

Brgds Jan Hoppe 

 

Comment
  1. Michael Kramer
  2. Wednesday, 8 January 2020 08:14 AM UTC
Correct. The original 2012-2011 script used ORCAScript for Get Latest.
  1. Helpful
  1. René Ullrich
  2. Wednesday, 8 January 2020 09:12 AM UTC
You may use Jenkins or other tools do get the sources from repository. But you need OrcaScript to load the Sources to PBLs.
  1. Helpful
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 7 January 2020 13:14 PM UTC
  2. PowerBuilder
  3. # 2

Hi Jan,

Yes, ORCAScript is the way forward.

Internal Info

Back in 2011-2012 I built a ORCAScript + PowerShell scriptset so that Bent B. could click on desktop icon and about half hour later we had a newly built install-package available on the customer FTP site. You may be able to track that down if anyone can help you find the old files.

Script used PB IDE with command-line options to build .EXE + .PBDs because ORCAScript didn't apply version data from the build project to the .EXE. With a little luck you can just replace that call with call to the command-line compiler and you are good to go.

 

HTH /Michael

Comment
  1. René Ullrich
  2. Wednesday, 8 January 2020 06:23 AM UTC
Hi Michael,

in my tests the OrcaScript does apply the version data to EXE. You have to use

set exeinfo property ...

commands in the OrcaScript.



e.g.

set exeinfo property copyright "My Copyright"

set exeinfo property productname "My Product"

set exeinfo property description "My Description"

set exeinfo property fileversion "1.0.0.0"

set exeinfo property fileversionnum "1,0,0,0"

set exeinfo property productversion "1.0.0.0"

set exeinfo property productversionnum "1,0,0,0"





  1. Helpful
  1. Michael Kramer
  2. Wednesday, 8 January 2020 09:10 AM UTC
Hi René, True, but that creates duplicate version info in .ORCA and PB project object.

I created an initial "deploy pipeline" to run at click of a button (later then automate fully). 1) Get Latest; 2) Create EXE+PBD-set; 3) Build installer; 4) Deploy to "downloads". My goal was "no duplicate" info. Version control also stored all images and DB upgrade scripts to be run at every customer site. "No duplicate" was very important for consistency.

Also, I'd rather let a team of PB developers know how to set version info in project painter than teach every team member to edit ORCA files.

Due to manual step in build/deploy it often took us 3 days to have installer ready for a test customer. We ended up having installer ready at effort below 30 seconds per deploy. Total pipeline completed within 30-45 minutes.
  1. Helpful
  1. Michael Kramer
  2. Wednesday, 8 January 2020 09:13 AM UTC
Mind, I won't take full credit alone. It was team effort to create the full pipeline and transition from all manual to max-automated process.
  1. Helpful
There are no comments made yet.
René Ullrich Accepted Answer Pending Moderation
  1. Tuesday, 7 January 2020 09:36 AM UTC
  2. PowerBuilder
  3. # 3
Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.