- John Niespodzianski
- PowerBuilder
- Tuesday, 18 June 2019 03: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
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.