diff options
| author | Tomasz Maczukin <tomasz@maczukin.pl> | 2016-04-19 14:42:50 +0300 |
|---|---|---|
| committer | Tomasz Maczukin <tomasz@maczukin.pl> | 2016-04-20 12:54:06 +0300 |
| commit | 4019b0d872bd2b183a06bdc832f5a100c8a88a00 (patch) | |
| tree | b8399ba84aaa087766a8d5f0bdd886d2c65d315d /doc | |
| parent | 0725c28069689ae958adfc140f0a47fa9596f641 (diff) | |
Fix some typos in documentation
[ci skip]
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ci/api/builds.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/ci/api/builds.md b/doc/ci/api/builds.md index 119dbbe9386..79761a893da 100644 --- a/doc/ci/api/builds.md +++ b/doc/ci/api/builds.md @@ -58,12 +58,12 @@ curl -X PUT "https://gitlab.example.com/ci/api/v1/builds/1234" -F "token=t0k3n" ### Incremental build trace update -Using this method you need to send trace content as a request body. You need also to provide the `Content-Range` header -with a range of sent trace part. Note, that you need to send parts in a proper order, so the begining of the part -must starts just after the end of the previous part. If you will mess the parts, then GitLab CI AIP will return `416 +Using this method you need to send trace content as a request body. You also need to provide the `Content-Range` header +with a range of sent trace part. Note that you need to send parts in the proper order, so the begining of the part +must start just after the end of the previous part. If you provide the wrong part, then GitLab CI API will return `416 Range Not Satisfiable` response with a header `Range: 0-X`, where `X` is the current trace length. -For example: if you receive `Range: 0-11` in the response, then your next part must contains `Content-Range: 11-...` +For example, if you receive `Range: 0-11` in the response, then your next part must contain a `Content-Range: 11-...` header and a trace part covered by this range. For a valid update API will return `202` response with: |