Forum Discussion

andylou's avatar
andylou
New Contributor
6 years ago

SoapUI Pro Version Control

Hi,

 

What is the proper way to collaborate on a source control tool, such as git.

Our team just started using soapUI pro, but have been having issues with overwritting each other's element.order and settings.xml files. 

We tried adding them to the .gitignore file, to reduce conflict. However we realized that if someone were to clone the repo onto a new location, they would then be missing the required files.

 

What should be the proper way of dealing with this?

 

Thanks,

Andy

3 Replies

Sort By
  • lakshmiarun's avatar
    lakshmiarun
    SmartBear Alumni (Retired)
    6 years ago

    Hi Andy,

     

    Thank you for your post. Here is the general guidelines on using the GIT integration Plugin:

     

    https://github.com/SmartBear/ready-git-plugin/wiki/About-the-Git-Integration-Plugin

    We would recommend that you enable the following two ReadyAPI settings:

    • Pretty print project files in the Preferences>WSDL dialog box.

    • Normalize line-break in the Preferences>UI dialog box.

    This will make your ReadyAPI project files friendlier to the “auto-merge” feature of Git.

    If you have any further issues, please open a ticket on our portal.

     

    Best,

    Lakshmi

    • andylou's avatar
      andylou
      New Contributor
      6 years ago

      We have tried using the git plugin, however it does not have the functionality we require. The git plugin does not give us granular control of directories in the project. Thus, we would have to make a new repository for every project we want to create.

       

      We have already enabled the two settings, pretty print project files, and normalize line-break.

       

      However, we still have conflicts in settings.xml and elements.order.

      • lakshmiarun's avatar
        lakshmiarun
        SmartBear Alumni (Retired)
        6 years ago

        Hi Andy,

         

        It is one repository per project, that is how it works. To drill down, could you please open a ticket? Are you using ReadyAPI 2.4?

         

        Best,

        Lkashmi