|
16 | 16 |
|
17 | 17 | 
|
18 | 18 |
|
19 |
| -### Basic Functionalities of Source Code Management |
20 |
| - |
21 |
| -* Add |
22 |
| - |
23 |
| -* Check Out |
24 |
| - |
25 |
| -* Check In |
26 |
| - |
27 |
| -* Check In message |
28 |
| - |
29 |
| -* Revision |
30 |
| - |
31 |
| -* Head |
32 |
| - |
33 |
| -* Changelog |
34 |
| - |
35 |
| -* Revert |
36 |
| - |
37 |
| -### Features of SCM |
38 |
| - |
39 |
| -* Backup and Restore |
40 |
| - |
41 |
| -* Synchronize |
42 |
| - |
43 |
| -* Earlier version review |
44 |
| - |
45 |
| -* Recent version restore |
46 |
| - |
47 |
| -* Version History |
48 |
| - |
49 |
| -* Owner History |
50 |
| - |
51 |
| -* Testing Environment |
52 |
| - |
53 |
| -* Branching and Merging |
54 |
| - |
55 |
| -### CI/CD |
56 |
| - |
57 |
| -In continuous integration practice, a **centralized server** regularly retrieves all new changes to the source code by developers and builds the **software application from scratch.** |
58 |
| - |
59 |
| -The **build and testing of the software is automated and every change or iteration to the software triggers an automated test run to ensure the desired delivery quality.** The central repository is always kept updated in continuous integration practice. |
60 |
| - |
61 |
| -Continuous deployment is the process of building, testing, and releasing the software from the build environment into the production environment automatically without human intervention. Continuous deployment automates the entire testing process and performs more tests on code blocks compared to the usual unit testing done on the code. |
62 |
| - |
63 |
| - |
64 |
| - |
65 | 19 | ### Version Control System (VCS)
|
66 | 20 |
|
67 | 21 | 
|
@@ -130,6 +84,54 @@ Continuous deployment is the process of building, testing, and releasing the sof
|
130 | 84 |
|
131 | 85 | * Periodic Packing of files
|
132 | 86 |
|
| 87 | +### Basic Functionalities of Source Code Management |
| 88 | + |
| 89 | +* Add |
| 90 | + |
| 91 | +* Check Out |
| 92 | + |
| 93 | +* Check In |
| 94 | + |
| 95 | +* Check In message |
| 96 | + |
| 97 | +* Revision |
| 98 | + |
| 99 | +* Head |
| 100 | + |
| 101 | +* Changelog |
| 102 | + |
| 103 | +* Revert |
| 104 | + |
| 105 | +### Features of SCM |
| 106 | + |
| 107 | +* Backup and Restore |
| 108 | + |
| 109 | +* Synchronize |
| 110 | + |
| 111 | +* Earlier version review |
| 112 | + |
| 113 | +* Recent version restore |
| 114 | + |
| 115 | +* Version History |
| 116 | + |
| 117 | +* Owner History |
| 118 | + |
| 119 | +* Testing Environment |
| 120 | + |
| 121 | +* Branching and Merging |
| 122 | + |
| 123 | +### CI/CD |
| 124 | + |
| 125 | + |
| 126 | + |
| 127 | +In continuous integration practice, a **centralized server** regularly retrieves all new changes to the source code by developers and builds the **software application from scratch.** |
| 128 | + |
| 129 | +The **build and testing of the software is automated and every change or iteration to the software triggers an automated test run to ensure the desired delivery quality.** The central repository is always kept updated in continuous integration practice. |
| 130 | + |
| 131 | +Continuous deployment is the process of building, testing, and releasing the software from the build environment into the production environment automatically without human intervention. Continuous deployment automates the entire testing process and performs more tests on code blocks compared to the usual unit testing done on the code. |
| 132 | + |
| 133 | + |
| 134 | + |
133 | 135 | ### GitHub
|
134 | 136 |
|
135 | 137 | 
|
|
0 commit comments