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

Resolved OrcaScript / Git Build Issue

  1. Issue
0
Votes
Undo
  1. John Niespodzianski
    John Niespodzianski
  2. PowerBuilder
  3. Tuesday, 18 June 2019 15:44 PM UTC

We've recently moved from VSS to TFS/Git for our source control.  

Everything is working great for development - we've opted to use Atlassian's SourceTree to help visually manage branches and workflow (via Git-Flow).  The ability to use feature branches has really helped us manage and develop large features simultaneously.

But the build process has had one glitch - OrcaScript 170 will not import the source objects into the PBLs.  It says the build is finished, but it actually fails to import and build.

I set it up according to the details in the help (link below) with no luck:

https://www.appeon.com/support/documents/appeon_online_help/pb2017r3/pbug/apbs04.html

In reading other Q&A's here regarding OrcaScript and Git, it appears that others are successfully using subfolders as part of their workspace/target layout (which we are as well).

But as a test, I "flattened" our folder structure so all PBLs were in one folder (and modified the ws_objects folder structure to match).  When I did this, the import and build worked successfully.

Has anyone else encountered this behavior?  If so, were you able to solve it?

Thanks,

John

 

 

  1. Git
  2. OrcaScript
Trigger definition
ApplyTheme issue with Win 10 Enterprise
Responses (2)
John Niespodzianski
John Niespodzianski Accepted Answer Pending Moderation
  1. Tuesday, 18 June 2019 20:31 PM UTC
  2. PowerBuilder
  3. # 1

I found the root cause of this issue - leaving this post up with this response in case someone else has the same issue.

When we added our project to Git, the ws_objects folder was created as expected.

However, it created duplicate entries for all PBLs that were in subfolders.  Removing these entries from the file system made OrcaScript happy.

Example:

C:\dev\one.pbl
C:\dev\two.pbl
C:\dev\three.pbl
C:\dev\subfolder\four.pbl

Results in:

C:\dev\ws_objects\source\one.pbl.src
C:\dev\ws_objects\source\two.pbl.src
C:\dev\ws_objects\source\three.pbl.src
C:\dev\ws_objects\source\four.pbl.src
C:\dev\ws_objects\source\subfolder\four.pbl.src

Removing the C:\dev\ws_objects\source\four.pbl.src folder from the file system did the trick.

 

 

Comment
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 19 June 2019 10:26 AM UTC
  2. PowerBuilder
  3. # 2

Hi John,

Generally, PB IDE won’t create this duplicated folder C:\dev\ws_objects\source\four.pbl.src

Please confirm if you have moved the saving path for four.pbl? For example, it was in C:\dev but later moved to C:\dev\subfolder.

If you didn’t move the saving path for four.pbl, then when you create a new test case, can you reproduce the issue? If you can still reproduce the issue, please let us know the reproducing steps in details so we can further analyze the issue.

 

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.