1. Giuseppe moglia
  2. PowerBuilder
  3. Friday, 10 September 2021 10:03 AM UTC

Hi Guys 

I've set up a Jenkins Job with SVN in order to build a PB2019R3 project

In this workspace I've several pbl and there are in different pbl (they are shared with other projects) windows with same name

i've seen during the orca refresh all these objects (.srw, ecc) are in the same directory so the last object overwrite the first one with the same name.

Is there a way to avoid this?

Thanks in advance for your help

 

Here my orca script:

start session
set debug true
scc set connect property localprojpath "C:\Program Files (x86)\Jenkins\workspace\MEP_8_8\Compila_0808\SC"
;localprojpath must point to the parent directory of ws_objects folder
scc set connect property logfile "C:\Program Files (x86)\Jenkins\workspace\MEP_8_8\svnorca.log"
scc set connect property logappend false
scc set connect property deletetempfiles "true"
scc connect offline
scc set target "C:\Program Files (x86)\Jenkins\workspace\MEP_8_8\Compila_0808\SC\mep.pbt" refresh_all importonly
scc exclude liblist "C:\Program Files (x86)\Jenkins\workspace\MEP_8_8\Compila_0808\SC\pbdom.pbd" "C:\Program Files (x86)\Jenkins\workspace\MEP_8_8\Compila_0808\SC\pbsoapclient.pbd"
scc refresh target 3pass
scc close
end session

Giuseppe moglia Accepted Answer Pending Moderation
  1. Wednesday, 24 November 2021 09:30 AM UTC
  2. PowerBuilder
  3. # 1

Thank you Ken

But Can I use the Autobuild forcing a 2019 Runtime?

Comment
  1. Ken Guo @Appeon
  2. Wednesday, 24 November 2021 09:38 AM UTC
Hi Guisepppe,



PBAutoBuild210 Does NOT support PB 2019(runtime) .



Regards, Ken
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Monday, 13 September 2021 10:44 AM UTC
  2. PowerBuilder
  3. # 2

Hi Giuseppe,

As far as I know, we have no adjustment to the ORCA part.
If everything works well with your PB 2017 R3 and have issue with PB 2019 R3, I suggest you report a bug to the Appeon Support system(https://www.appeon.com/standardsupport/newbug) and upload small cases there, including a PB 2017 R3 and a PB 2019 R3 case, so that Appeon Support will assign it to specialized staff.

Regards,
Ken

Comment
There are no comments made yet.
Giuseppe moglia Accepted Answer Pending Moderation
  1. Monday, 13 September 2021 07:21 AM UTC
  2. PowerBuilder
  3. # 3

Thank you Ken

but now we have adopted PB2019 R3 and differently from PB 2017 R3 pb compiler needs orca to refresh libraries. pbc2017 refreshed itself pbls so no problem

 

Could you confirm me pbc2019 refresh pbls as pbc2017 did?

 

Thank you

Comment
There are no comments made yet.
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Saturday, 11 September 2021 00:27 AM UTC
  2. PowerBuilder
  3. # 4

Hi Giuseppe,

ORCA is a legacy feature on PowerBuilder. It does have some defact in its design. In other words, when you have multiple PBLs with the same-named objects, it will have this conflict.

Currently, I suggest that you work it around using the following method:
Say you have test1.pbl and test2.pbl contain the same-named objects. You need to put test1.pbl and test2.pbl in different sub-folder, such as
AppFolder\sub1\test1.pbl
AppFolder\sub2\test2.pbl

BTW, PB 2021 has a new feature PBAutoBuild. In comparison to ORCA, it is much easy to use and comes with more powerful build functions. And it doesn’t have this bug. I suggest that you check out this link:
https://docs.appeon.com/pb2021/pbug/ch07s03.html#Tutorial_Building_your_Application_project_with_commands 

Regards,
Ken

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.