Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
iv
gitlab-ce
Commits
4019b0d8
Commit
4019b0d8
authored
Apr 19, 2016
by
Tomasz Maczukin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix some typos in documentation
[ci skip]
parent
0725c280
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
5 deletions
+5
-5
doc/ci/api/builds.md
doc/ci/api/builds.md
+4
-4
lib/ci/api/builds.rb
lib/ci/api/builds.rb
+1
-1
No files found.
doc/ci/api/builds.md
View file @
4019b0d8
...
...
@@ -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 start
s 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:
...
...
lib/ci/api/builds.rb
View file @
4019b0d8
...
...
@@ -57,7 +57,7 @@ module Ci
# Body:
# content of logs to append
# Headers:
# Content-Range (required) - range of con
n
tent that was sent
# Content-Range (required) - range of content that was sent
# BUILD-TOKEN (required) - The build authorization token
# Example Request:
# PATCH /builds/:id/trace.txt
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment