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

Resolved PB 2022 with DevOps source control

  1. Advice
0
Votes
Undo
  1. Connie Dove
    Connie Dove
  2. PowerBuilder
  3. Friday, 3 March 2023 23:46 PM UTC

Good afternoon,

  We are migrating from PB 2019R3 to PB 2022.  We were able to set up our applications in the DevOps repository and it worked kinda.  It got to be too much of a hassle to use DevOps because of issues with conflicts all the time, or the branches getting messed up.  

  I thought I heard that 2022 will do a better job connecting to DevOps and will be easier to manager.  

Is that a true statement?  How is it working for others?

Thanks

  1. Azure
  2. PowerBuilder
Application performance is too slow
Powerclient dot net 6 core pre-requisite install o...
Responses (3)
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 7 March 2023 05:07 AM UTC
  2. PowerBuilder
  3. # 1

Hi Connie,

 

The conflicts of PBLs have always been the most common problem in PB source code management. PB 2022 does not upload PBLs by default. Every time the code is pulled, it will re-generate the PBLs (or Refresh PBL). The problem of PBL conflicts will be eliminated, and the chance of conflicts from other objects is smaller and easier to fix.

 

I hope that the source control improvement of PB 2022 can bring you a good experience.

 

Regards,

Kitty

Comment
There are no comments made yet.
Connie Dove
Connie Dove Accepted Answer Pending Moderation
  1. Monday, 6 March 2023 23:30 PM UTC
  2. PowerBuilder
  3. # 2

Some of the conflicts was happening with the same developer pushing their code to devops.  They would work on a fix, push their code and then make some other changes and push the code and kept getting conflicts.

There were times when everything appeared to work great and no conflicts and could see the date changed in the ws_objects folder.  Then awhile later when we would fetch those changes, some of the changes made would be gone.  

We finally just stopped trying to use it for now, but with moving to 2022, our boss wants us to look into it again.  Currently we only have 2 developers doing powerbuilder.  We try not to work on the same application at the same time to avoid issues.

 

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 4 March 2023 15:24 PM UTC
  2. PowerBuilder
  3. # 3

Conflicts are likely to happen if two or more developers simultaneously work on the same object since Git doesn't lock the file.  

As far as branches getting messed up, not sure what exactly you are experiencing.  Could you elaborate?

PB 2022 source control features have been enhanced as follows: https://docs.appeon.com/pb/whats_new/Source_control_2022_enhancements.html

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.