Changes for page Tracking Type
Last modified by Achraf El Kari on 2022/06/13 13:17
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - GITendpoints1 +Tracking Type - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. omoustaghfir1 +XWiki.aelkari - Content
-
... ... @@ -4,13 +4,25 @@ 4 4 5 5 = Introduction = 6 6 7 - Gitendpointstake advantageofallgit commands knownand needed tocreateversionsoffiles.7 +We will go through all endpoints needed to manage the Tracking type entity. 8 8 9 9 = Endpoints = 10 10 11 -|(% style="width:166px" %)**URL [method]**|(% style="width:189px" %)**Description**|(% style="width:383px" %)**Input example**|(% style="width:449px" %)**Output example** 12 -|(% style="width:166px" %)/rest/git/getstatus [GET]|(% style="width:189px" %)get all files that have been modified or untracked|(% style="width:383px" %)(no input required)|(% style="width:449px" %){{code language="JSON"}} 13 -{ 11 +**PS :** __//For all those endpoints, the env params is andatory on the header, otherwise you got an error 400 (BAD PARAMS).//__ 12 + 13 + 14 +|(% style="width:166px" %)**URL [method]**|(% style="width:238px" %)**Description**|(% style="width:599px" %)**Input example**|(% style="width:449px" %)**Output example** 15 +|(% style="width:166px" %)((( 16 +/rest/trackingType [GET] 17 + 18 + 19 +hedear : Authorization + env => Mandatory 20 + 21 +)))|(% style="width:238px" %)((( 22 +get **all **tracking Type of the giving environment ==> 23 + 24 +order, orderLine... 25 +)))|(% style="width:599px" %)(no input required)|(% style="width:449px" %){{code language="JSON"}}{ 14 14 "timestamp": 1620216790744, 15 15 "status": "200", 16 16 "data": [ ... ... @@ -24,7 +24,7 @@ 24 24 } 25 25 ] 26 26 }{{/code}} 27 -|(% style="width:166px" %)/rest/git/history [GET]|(% style="width: 189px" %)get all commits history, with their IDs ,authors ,messages, dates and if considired as current version or not |(% style="width:383px" %)(no input required)|(% style="width:449px" %){{code language="JSON"}}{39 +|(% style="width:166px" %)/rest/git/history [GET]|(% style="width:238px" %)get all commits history, with their IDs ,authors ,messages, dates and if considired as current version or not |(% style="width:599px" %)(no input required)|(% style="width:449px" %){{code language="JSON"}}{ 28 28 "timestamp": 1620217014704, 29 29 "status": "200", 30 30 "data": [ ... ... @@ -44,7 +44,7 @@ 44 44 } 45 45 ] 46 46 }{{/code}} 47 -|(% style="width:166px" %)/rest/git/commit [POST]|(% style="width: 189px" %)commit changes in files with a message|(% style="width:383px" %){{code language="JSON"}}{59 +|(% style="width:166px" %)/rest/git/commit [POST]|(% style="width:238px" %)commit changes in files with a message|(% style="width:599px" %){{code language="JSON"}}{ 48 48 "files": 49 49 [ 50 50 {"fileName" : "newFile.xml"}, ... ... @@ -66,13 +66,13 @@ 66 66 /rest/git/switchComit/{id} 67 67 68 68 [GET] 69 -)))|(% style="width: 189px" %)(((81 +)))|(% style="width:238px" %)((( 70 70 switch to a certain version and return the history of all commits. 71 71 72 72 **__NB __**: if there are some modified files in the current version, these files will be moved to a new directory called : 73 73 74 74 .../archive/git-{timestamp} 75 -)))|(% style="width: 383px" %)(((87 +)))|(% style="width:599px" %)((( 76 76 the {id} in the URL should be replaced by the id of the wanted commit. 77 77 78 78 eg : ... ... @@ -104,9 +104,9 @@ 104 104 } 105 105 {{/code}} 106 106 ))) 107 -|(% style="width:166px" %)/rest/git/update [GET]|(% style="width: 189px" %)(((119 +|(% style="width:166px" %)/rest/git/update [GET]|(% style="width:238px" %)((( 108 108 Integrates and pulls changes from a remote repository into the current branch. 109 -)))|(% style="width: 383px" %)(no input required)|(% style="width:449px" %)(((121 +)))|(% style="width:599px" %)(no input required)|(% style="width:449px" %)((( 110 110 it returns a success message. 111 111 112 112 eg : ... ... @@ -119,13 +119,13 @@ 119 119 } 120 120 {{/code}} 121 121 ))) 122 -|(% style="width:166px" %)/rest/environment/init [POST]|(% style="width: 189px" %)(((134 +|(% style="width:166px" %)/rest/environment/init [POST]|(% style="width:238px" %)((( 123 123 Clone a git repository into the directory of the current environment, 124 124 125 125 if it doesn't exist it creates a new directory and initialize the repo, 126 126 127 -if the directory exists, the endpoint rename the directory withand create a new one and clone the repository.128 -)))|(% style="width: 383px" %)(no input required)|(% style="width:449px" %)(((139 +if the directory exists, the endpoint renames the directory and creates a new one and clones the repository. 140 +)))|(% style="width:599px" %)(no input required)|(% style="width:449px" %)((( 129 129 it returns a "success" message : 130 130 131 131 eg : ... ... @@ -134,9 +134,86 @@ 134 134 { 135 135 "timestamp": 1620229625932, 136 136 "status": "200", 137 - "data": "o k"149 + "data": "Repository initialized successfully !" 138 138 } 139 139 {{/code}} 140 140 ))) 153 +|(% style="width:166px" %)/rest/git/checkout/{branch} [POST]|(% style="width:238px" %)switch to a certain branch|(% style="width:599px" %)((( 154 +the {branch} must be replaced by the name of the branch destination. 141 141 156 +eg : /rest/git/checkout/master 157 + 158 + /rest/git/checkout/develop 159 +)))|(% style="width:449px" %)((( 160 +it returns a "success" message of checkout branch. 161 + 162 +eg : 163 + 164 +{{code language="JSON"}} 165 +{ 166 + "timestamp": 1620229625932, 167 + "status": "200", 168 + "data": "switched to branch : master" 169 +} 170 +{{/code}} 171 +))) 172 +|(% style="width:166px" %)((( 173 +/rest/git/newbranch/{branch} 174 + 175 +[POST] 176 +)))|(% style="width:238px" %)create and switch to a new branch |(% style="width:599px" %)((( 177 +the {branch} must be replaced by the name of the branch destination. 178 + 179 +eg : 180 + 181 + /rest/git/checkout/newBranch 182 +)))|(% style="width:449px" %)((( 183 +it returns a "success" message of the branch creation. 184 + 185 +eg : 186 + 187 +{{code language="JSON"}} 188 +{ 189 + "timestamp": 1620229625932, 190 + "status": "200", 191 + "data": "new branch has been created : newBranch" 192 +} 193 +{{/code}} 194 +))) 195 +|(% style="width:166px" %)/rest/git/revert [POST]|(% style="width:238px" %)switch the modified file to the initial head version. |(% style="width:599px" %){{code language="JSON"}}{ 196 +"files": 197 +[ 198 +{"fileName" : "newFile.xml"}, 199 +{"fileName" : "/dir/modifiedFile.pdf"} 200 +] 201 +}{{/code}}|(% style="width:449px" %)((( 202 +it returns a "success" message. 203 + 204 +eg : 205 + 206 +{{code language="JSON"}} 207 +{ 208 + "timestamp": 1620229625932, 209 + "status": "200", 210 + "data": "the selected files has been synchronized to HEAD successfully !" 211 +} 212 +{{/code}} 213 +))) 214 + 215 += Errors = 216 + 217 +below, you can find an example of technical and functional errors : 218 + 219 +{{code language="JSON"}} 220 +{ 221 + "timestamp": 1620221672951, 222 + "status": "500", 223 + "error": "JSON file is not valid", 224 + "thechnicalError": "JSONObject[\"fileName\"] not found." 225 +} 226 +{{/code}} 227 + 228 +the functional error is shown with the JSON key "error", while technical error is stored in the "thechnicalError" key. 229 + 230 + 142 142 == ==