Check Code Into Subversion

Check Code Into Subversion

Instructions

Once you have run your project and you are satisfied with your test results, you will want to check in code to our repository. All of our code is stored in a central repository hosted in our data center. The subversion tool, Tortoise SVN, is installed on your computer to assist you in the process. Find the directory where the code you want to check in is located. Right click on the folder and select SVN Commit. Review each file that you want to check in to review the changes. You will do this by right clicking on the name of the file and choosing Compare with Base. This will bring up a window showing the repository code and any changes in the version to be checked in. Review these changes and if you are satisfied, close the dialog. If you are not satisfied, go back into your code and make any additional changes. Under the Message text box on the top of the screen, type in the changes you made and why they were made.  Click on the OK button to commit the code.

You will not need to check in the jndi.xml file. This is a local file that says what database to run your tests against.

Once the code is checked in, it will be added to the repository and then run against the tests stored on TeamCity. TeamCity is a tool that allows a standardized set of tests to be run against all code in the code base. You will receive an email from TeamCity if something you check in does not run correctly. You can then log into TeamCity and see why the test has failed. Use this to change or fix any tests on your local environment.

 


    • Related Articles

    • Subversion Guide

      We use a version control software called Subversion. With this we can check out repositories, create branches, commit code changes, and do many other cool things. We don’t use the command line to interact with Subversion, rather we use TortoiseSVN, ...

    • FullCount Subversion Repositories

      FullCount Subversion Repositories Introduction Subversion is a software tool for organizing and managing different versions of source code for computer programs. It is primarily used for managing plain text files such as source code, configuration ...

    • Code Review Checklist

      Before asking for code to be reviewed, the following steps should be completed. This will ensure a smooth review process and help code to get checked in more quickly. Javadocs created/updated Method and class level comments added Back office ...

    • Code Review Policy

      Code Review Policy Objective: The primary goal of our code review process is to ensure high-quality, maintainable, and efficient code that aligns with the team's standards and best practices. Code reviews serve as a collaborative effort to enhance ...

    • Run A Maven Project

      Instructions Once you have run your project and you are satisfied with your test results, you will want to check in code to our repository. All of our code is stored in a central repository hosted in our data center. The subversion tool, Tortoise ...