Methods and Systems for Validating Changes Submitted to a Source Control System
In accordance with embodiments, there are provided mechanisms and methods for validating changes before submission to a source control system, which can provide developers with a remote server where changelists may be uploaded, specified tests may be run, and results may be returned to the developer. The ability to provide a remote server for changelist uploads, automated source code compilations, automated test executions, and the automatic return of results, tends to enable developers to quickly and efficiently make source code design changes and avoid to build breakages.
1 . A method for validating source code changes prior to submission to a source control system, the method comprising the steps of:
receiving, at a server machine from a remote developer machine, at least one source code change for validation before submission to a source control system;
building, via a pre-check-in validation system associated with the server machine, an application that includes the at least one source code change for validation before submission to a source control system;
testing, via the pre-check-in validation system associated with the server machine, the application that includes the at least one source code change for validation prior to submission to a source control system; and
sending, notification of building and testing results of the at least one source code change, from the pre-check-in validation system to the developer machine.
2 . The method of claim 1 , further comprising:
automatically submitting the at least one source code change to a source control system of the pre-check-in validation system if the building and testing of the application that includes the at least one source code change is successful.
3 . The method of claim 2 , wherein automatically submitting the at least one source code change is based on developer credentials.
4 . The method of claim 1 , wherein the at least one source code change for validation before submission to a source control system is included in a changelist of source code changes.
5 . The method of claim 1 , wherein the step of testing uses functional tests to verify the application performs as expected.
6 . The method of claim 1 , wherein the step of testing uses tests organized into test suites.
7 . The method of claim 1 , wherein the step of testing uses functional tests organized into test suites.
8 . The method of claim 1 , wherein the pre-check-in validation system includes an automated build environment configured to automatically build and test source code before submission to a source control system.
9 . The method of claim 1 , wherein the developer machine remotely sends to a server machine associated with a pre-check-in validation system, functional tests for testing the application before submission to a source control system.
10 . The method of claim 1 , wherein the step of building is executed automatically by the pre-check-in validation system.
11 . The method of claim 1 , wherein the step of testing is executed automatically by the pre-check-in validation system.
12 . The method of claim 1 , wherein the steps of building and testing are executed automatically by the pre-check-in validation system.
13 . The method of claim 1 , further comprising:
automatically submitting the at least one source code change to a source control system of the pre-check-in validation system if the building and testing of the application that includes the at least one source code change is successful, wherein automatically submitting the at least one source code change is based on developer credentials, and wherein the pre-check-in validation system includes an automated build environment configured to automatically build and test source code before submission to a source control system,
the building and testing are executed automatically by the pre-check-in validation system, the at least one source code change for validation before submission to a source control system is included in a changelist of source code changes,
the testing uses functional tests organized into test suites, and
the developer machine remotely sends to a server machine associated with a pre-check-in validation system, functional tests for testing the application before submission to a source control system.
14 . A computer-readable medium storing one or more sequences of instructions for causing one or more processors to implement a method for validating source code changes prior to submission to a source control system, the method comprising the steps of:
receiving, at a server machine from a remote developer machine, at least one source code change for validation before submission to a source control system;
building, via a pre-check-in validation system associated with the server machine, an application that includes the at least one source code change for validation before submission to a source control system;
testing, via the pre-check-in validation system, the application that includes the at least one source code change for validation before submission to a source control system; and
sending, notification of building and testing results of the at least one source code change from the pre-check-in validation system to the developer machine.
15 . The computer readable medium of claim 14 , the method further comprising:
automatically submitting the at least one source code change to a source control system of the pre-check-in validation system if the building and testing of the application that includes the at least one source code change is successful.
16 . The computer readable medium of claim 14 , further comprising:
automatically submitting the at least one source code change to a source control system of the pre-check-in validation system if the building and testing of the application that includes the at least one source code change is successful, wherein the automatically submitting of the at least one source code change is based on developer credentials, and wherein the pre-check-in validation system includes an automated build environment configured to automatically build and test source code before submission to a source control system,
the building and testing are executed automatically by the pre-check-in validation system,
the at least one source code change for validation before submission to a source control system is included in a changelist of source code changes,
the testing uses functional tests organized into test suites, and
the developer machine remotely sends to a server machine associated with a pre-check-in validation system, functional tests for testing the application before submission to a source control system.
17 . A validation system for validating source code changes prior to submission to a source control system, the validation system comprising:
a processor system;
volatile memory; and
non-volatile memory including at least one machine readable medium carrying one or more sequences of instructions causing the processor system to implement a method comprising the steps of:
receiving, at a server machine from a remote developer machine, at least one source code change for validation before submission to a source control system;
building, via a pre-check-in validation system associated with the server machine, an application that includes the at least one source code change for validation before submission to a source control system;
testing, via the pre-check-in validation system, the application that includes the at least one source code change for validation before submission to a source control system; and
sending, notification of building and testing results of the at least one source code change from the pre-check-in validation system to the developer machine.
18 . The system of claim 17 which, if the building and testing of the application of the at least one source code changes is successful, automatically submits the at least one source code change to a source control system of the pre-check-in validation system.
19 . The system of claim 17 , further comprising:
automatically submitting the at least one source code change to a source control system of the pre-check-in validation system if the building and testing of the application that includes the at least one source code change is successful, wherein the automatically submitting of the at least one source code change is based on developer credentials, wherein the pre-check-in validation system includes an automated build environment configured to automatically build and test source code before submission to a source control system,
the building and testing are executed automatically by the pre-check-in validation system,
the at least one source code change for validation before submission to a source control system is included in a changelist of source code changes,
the testing uses functional tests organized into test suites, and
the developer machine remotely sends to a server machine associated with a pre-check-in validation system, functional tests for testing the application before submission to a source control system.