Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Speeding up continuous integration and build time

  1. Advice
1
Votes
Undo
  1. Arnaud Bailly
    Arnaud Bailly
  2. PowerBuilder
  3. Tuesday, 14 April 2020 09:38 AM UTC

Hello,

We are currently building a large-ish PowerBuilder (2017 but we are in the process of migrating to 2019) application using Microsoft's DevOps pipelines. Our current build script takes quite a lot of time as we:

  • cleanup everything
  • copy all sr* files from ws_objects directory to toplevel directory
  • generate the PBLs from the source files using orcascript
  • then compile to PBDs and produce .exe using pbc190.exe

How could we speed things up? I noticed that generating PBDs from PBLs is relatively fast but of course requires to check-in the PBLs in version control (git). Are there any downsides to this approach?

Thanks for any help, tips and tricks, advices you could provide

  1. Build
  2. Compiler
  3. PowerBuilder (Appeon)
Using the Microsoft Text Driver ODBC driver to rea...
Print PDF files from folder in powerbuilder applic...
Responses (2)
Sezer Gülap
Sezer Gülap Accepted Answer Pending Moderation
  1. Monday, 26 April 2021 10:05 AM UTC
  2. PowerBuilder
  3. # 1

Hello Arnaud,

We have the exact same situation. We have prepared an orcascript configuration. It refresh&build PBLs from scratch and generate PBDs and EXE. It takes about ~20 mins. We use Azure DevOps Server Pipeline configuration, too. I see the case as resolved. How did you speed it up?

Thank you

Comment
René Ullrich
  1. René Ullrich
  2. Monday, 3 May 2021 07:27 AM UTC
But keep in mind! A "Refresh" with OrcaScript can only insert new objects and update existing objects in a PBL. It will not delete an object from PBL if it was deleted from source control!

We also tried OrcaScript to build PBLs from source control. Problem is that it may fail on first try with compile errors if there are complex object dependencies. So you have to run the OrcaScript twice what maes it slowly.

Currently we try to use PowerGen. It seems to work better.
  1. Helpful
Sezer Gülap
  1. Sezer Gülap
  2. Monday, 3 May 2021 08:29 AM UTC
We delete all PBLs before running OrcaScript, so it creates fresh new files from source code. As you said, because of compilation errors on first try, i use 3pass and it seems working for now. OrcaScript process takes about 9 minutes now. Full CI/CD process including creating compressed update package and installer takes about 25 minutes. It is not great but ok for now. I don't want to deal with a new purchase process for PowerGen on a governmental organization..



Thank you
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 14 April 2020 14:00 PM UTC
  2. PowerBuilder
  3. # 2

Here is a crazy idea not sure it will work.  Try using pbc190.exe to generate just the exe and PBD that corresponds with the PBL containing your application and project object.  The rest of the PBLs just manually by hand copy create duplicate and rename the extension from PBL to PBD.  If this works, then you could write a script to automate.

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 21 April 2020 14:48 PM UTC
Arnaud said files not objects.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Tuesday, 21 April 2020 15:16 PM UTC
I'm pretty sure the files he is talking about are the .sr* files.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 21 April 2020 15:29 PM UTC
Oh, I see.
  1. Helpful
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.