• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • CI using git pull & AutoCompile: Changes not integrated into build

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

Resolved CI using git pull & AutoCompile: Changes not integrated into build

  1. Issue
0
Votes
Undo
  1. Michael W.
    Michael W.
  2. PowerBuilder
  3. Friday, 23 February 2018 08:17 AM UTC

Hi,

I'm trying to set up continuous integration using Git and AutoCompile. 

The (simplified) scenario looks as follows:

  1. Run git pull to get the latest version of the sources. 
  2. Run AutoCompile (pbc170.exe) to compile/deploy the sources. 

The problem I encounter is that the changes (to the *.sr* files from commits) are not being integrated into the build. I checked the contents of the pbl files and indeed they don't contain the changes from the commits. 

In PowerBuilder IDE, you can do a "Refresh" to update the .pbl files (from the *.sr* files) after doing a git pull. I tried to do the same by using OrcaScript but no luck so far. I did a scc connect offline followed by scc refresh target (basically the same as can be found at https://community.appeon.com/groups/powerbuilder/continuous-integration-powerbuilder-2017-bonobo-git-and-jenkins ). When I look at the contents of the pbl files I don't see the changes that should have been integrated. Also, when I compile/deploy using pbc170.exe, the changes are not there. 

I read the following blog posts:
https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/175-continuous-integration-with-powerbuilder-2017-bonobo-git-and-jenkins

https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/178-revisiting-continuous-integration-with-powerbuilder-2017-bonobo-git-and-jenkins

Any ideas on how I can "refresh" the *.pbl files using the command line (AutoCompile)?

  1. .EXE
PB 2019 Install Issue
Powerscript Editor
Responses (5)
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Friday, 23 February 2018 15:19 PM UTC
  2. PowerBuilder
  3. # 1

Hi Michael,

 

Have you verified that your local .PBLs are set with proper read/write permissions? Also the folder containing them? If so, and the problem persists, please open a support ticket so we can analyze your case.

 

Regards,

Comment
Michael W.
  1. Michael W.
  2. Monday, 26 February 2018 06:49 AM UTC
Hi Govinda,



Yes, read/write settings are correct and the folder contains the pbl files, but older versions of them. So for example, the latest commit contains only the *.sr* file. I haven't checked in (commited) the pbl files again. I checked in the pbl files only once in the beginning in order to have them. 



I will open a support ticket. 

  1. Helpful
Michael W.
  1. Michael W.
  2. Wednesday, 28 March 2018 05:41 AM UTC
I see that it's listed as a known issue in the release notes. So hope that it will be fixed soon. 

  1. Helpful
Dana Morano
  1. Dana Morano
  2. Tuesday, 15 January 2019 17:16 PM UTC
Hi did you open a support ticket - is this resolved - it sounds exactly like the same issue we are facing?
  1. Helpful
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Saturday, 24 February 2018 01:52 AM UTC
  2. PowerBuilder
  3. # 2

You should consider building the PBLs from the source code that was committed rather than from the PBLs that were in source control.  You might see https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/178-revisiting-continuous-integration-with-powerbuilder-2017-bonobo-git-and-jenkins, although that was written prior to R2 when I was using the PBSoftware MSSCCI bridge to connect to Git.

Comment
Michael W.
  1. Michael W.
  2. Monday, 26 February 2018 06:52 AM UTC
Hi Bruce,



Thanks and yes that's what I've been trying to do. 



I'm trying to build/regenerate/update the pbl files using the OrcaScript that can be found at https://community.appeon.com/groups/powerbuilder/continuous-integration-powerbuilder-2017-bonobo-git-and-jenkins



​But the problem is that my changes (to the *.sr* files) are not getting integrated/included in the pbl files I (re)generate. 

  1. Helpful
There are no comments made yet.
Michael W.
Michael W. Accepted Answer Pending Moderation
  1. Wednesday, 28 March 2018 05:43 AM UTC
  2. PowerBuilder
  3. # 3

An update on this: 

I see that it's listed as a known issue in the release notes. Hope that it will be fixed soon. 

Comment
Tareq Haschemi
  1. Tareq Haschemi
  2. Friday, 4 May 2018 11:17 AM UTC
Are there any news? I am looking for a fix...i have the same issues.

  1. Helpful
There are no comments made yet.
patrice domange
patrice domange Accepted Answer Pending Moderation
  1. Friday, 31 May 2019 23:04 PM UTC
  2. PowerBuilder
  3. # 4

Hi Michael,

What you can do while waiting this issue being solved is to force the PBLs to contains all the last changes using the following manual procédure :

{Inside PB IDE - Getting last changes from server}

1.Do a GIT Pull

2. Do a GIT Refresh

{Inside PB IDE - after Codes changes }

1. Do Full build & run Unit Tests, if any

2. Do GIT Commit

3. Do Upload PBL

{PB IDE closed, using Tortoise Git}

1. Do Push

That way, you are forcing the PBL to contains all sources changes and to push it onto server.

These changes will be then directly available from the pulled branch and can be directly addressed to the Automatic Compiler as originally expected.

 

 

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

Hi Michael,

You can use the following method to resolve this issue:
1. Firstly, please make sure the developers are using Git/SVN on PB as source control: you will see there is a ws_objects folder on Git/SVN server, which contains the latest source code for all PB objects.
2. Use a Git client like TortoiseGit to download the latest files, mainly the entire ws_objects folder.
3. Use OrcaScript to import the source code files from ws_objects into the PBLs. Here is an example:
start session
scc set connect property localprojpath "d:\testcase"
;localprojpath must point to the parent directory of ws_objects folder
scc set connect property logfile "d:\testcase\orca.log"
scc set connect property logappend false
scc set connect property deletetempfiles "true"
scc connect offline
scc set target "d:\testcase\test0603.pbt" "refresh_all importonly"
scc refresh target "3pass"
…

4. At this moment, the PBLs now include the latest source code. You can then use OrcaScript to deploy PBLs into an exe. Here is an example:
…
build library "d:\testcase\test0603.pbl" "" pbd
build executable "d:\testcase\test0603.exe" "" "" "y" newvstylecontrols
scc close
end session

Of course, if you don’t want to use OrcaScript in step 4, you can also use PBC to deploy it as an exe.

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.