1. Song Tom
  2. PowerBuilder
  3. Tuesday, 11 June 2019

recently our TFS 2012 want to migrate to MS devops 2019 to catch the latest DEVOPS trend, but seems only TFS 2013 explore and related scc plugin can support that,
but when we installed,  there is error message

*Phenomenon:
each check-in would prompt a  "Parameter is not valid" which lead to a fail
  
*Reproduce Steps:
1. download and install teamexplore 2013 and scc plugin (Visual Studio Team Foundation Server MSSCCI Provider (64-bit).msi)

2. create pb workspace  and connect to the DEVOPS server

3. add source code and make change then check-in, currently, this would be fine


4. check out code and make change again, and re-check in, error  "Parameter is not valid"


5. whatever check-in , error  "Parameter is not valid"  still prompt

Remarks:
can help us find a solution on that, our TFS SERVER is MS DEVOPS 2019 and TFS team explore client version 2013 with its SCCI 64BIT plugin

Song Tom Accepted Answer Pending Moderation
0
Votes
Undo

I think maybe it is a small issue, whenever I restart the PB, the check-in would be fine, but it always fail after that during PB IDE open.

Comment
Please open a support ticket. This does not sound like a configuration issue.
  1. Armeen Mazda
  2. Tuesday, 11 June 2019
There are no comments made yet.
  1. Tuesday, 11 June 2019
  2. PowerBuilder
  3. # 1
Song Tom Accepted Answer Pending Moderation
0
Votes
Undo

Dear Armeen:

      Thanks your advice, The reason we use TFS is due to complexity on Git for PowerBuilder, The difficult two phrases of commit and push can often lead to a confusion,  and multiple user change in one pbl can always got error when push code; the handful thing is that we even cannot directly figure out whether local repository has been synced with the git server. so base on our friendly experience on TFS 2012 before, we have suggest our boss using TFS, but we are disappointed to get error like that, can help us to resolve it?  is there better way for source control on server and client mode can cater for the DEVOPS CI/CD trend?

Comment
You can still use Git and enable file locking. If file locked then it should eliminate merge conflicts.
  1. Armeen Mazda
  2. Tuesday, 11 June 2019
There are no comments made yet.
  1. Tuesday, 11 June 2019
  2. PowerBuilder
  3. # 2
Armeen Mazda Accepted Answer Pending Moderation
0
Votes
Undo

For a Git repository, which is what MS DevOps 2019 supports, you should be using the native Git interface of PB 2019 instead of the MSCCI interface.  The TortoiseGit client should interface with the Git repository, and PB 2019 has built-in support for the TortoiseGit client.  We kept the MSCCI interface in the product purely for backwards compatibility with older version control systems, such as TFVC.

Here are some links you may find useful:

https://docs.microsoft.com/en-us/azure/devops/user-guide/code-with-git?view=azure-devops

https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/202-powerbuilder-2017-r3-new-feature-git-enhancements

https://community.appeon.com/index.php/articles-blogs/tips-tricks-techniques-articles/17-powerbuilder/227-tips-on-using-git-with-powerbuilder

https://community.appeon.com/index.php/articles-blogs/tips-tricks-techniques-articles/17-powerbuilder/238-working-with-branches-in-git

 

Comment
There are no comments made yet.
  1. Tuesday, 11 June 2019
  2. PowerBuilder
  3. # 3
  • 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. Learn More