Forum Discussion

sdeevers's avatar
sdeevers
Contributor
6 years ago

Is there a way to rollback to the Ready API 2.5.0 version?

We are having issues post update to Ready API 2.6.0 with GIT and wanted to know if there is a way to rollback to the 2.5.0 version.

 

Any help would be greatly appreciated!

  • Lucian's avatar
    Lucian
    6 years ago

    You can remove this by editing the settings.xml of the project. There should be a line like "updated_to_2.6.0=true" or something like this. If you remove that you'll get no more errors.

  • nmrao's avatar
    nmrao
    Champion Level 3
    6 years ago
    It should be possible. Please check the installation location and each version be installed in the separate directory. You can invoke the tool of the particular version from command line ReadyAPI-<version>/bin/readyapi.bat (.sh depending on the os).

    Only thing is if the project is opened in higher version and changes are saved, there might be chances that the same project could not be opened in lower version later. But if the project artifacts are under repository like svn / git / cvs, the you could always go back to compatible revison.
    • sdeevers's avatar
      sdeevers
      Contributor
      6 years ago

      Thanks Rao.

       

      I thought of that, but once the installation occurs, the previous installation directory executables, bat files, etc., are removed so you can no longer take that approach. 

  • edweerdt's avatar
    edweerdt
    Contributor
    6 years ago

    Experiencing git issues too with 2.6.0. What are yours?

    We are having discard and pull issues.

    • sdeevers's avatar
      sdeevers
      Contributor
      6 years ago

      The GIT issues are with Discard and Pull and Commit. After performing a Discard, and then attempting a Pull, we receive the message "There are uncommitted changes. Commit or revert your changes before retrieving data from a remote repository.". We receive the same error when we attempt to Commit changes as well. You can perform a Push (not recommened if you have people on the 2.5.0 or earlier releases) as it will bypass and place the changes in the repository causing issues for those in previous releases.

       

      We generated a ticket, 00333091 for this issue and are working with support.