summaryrefslogtreecommitdiff
path: root/app/views/shared/projects/_project.html.haml
diff options
context:
space:
mode:
authorKamil Trzciński <ayufan@ayufan.eu>2015-10-13 14:33:00 +0000
committerKamil Trzciński <ayufan@ayufan.eu>2015-10-13 14:33:00 +0000
commite3edd53ae420e3cd581be9ac1029df8a0c93daab (patch)
tree2f2f29e775115552ac479a6fb377c8e872f74620 /app/views/shared/projects/_project.html.haml
parent5313c38858d4c22ea725d3b5a4499be9ccabe38a (diff)
parente7cc554cc181cbb850f89af26e64a9ab56116f28 (diff)
downloadgitlab-ce-e3edd53ae420e3cd581be9ac1029df8a0c93daab.tar.gz
Merge branch 'commit_status' into 'master'
Implement Commit Status API This is preliminary implementation of Commit Status API, pretty much compatible with GitHub. 1. The Commit Statuses are stored in separate table: ci_commit_status. 2. The POST inserts a new row. 3. To POST execute GitLab API `post :id/repository/commits/:sha/status`. This accepts dual authorization: - Using authorized user - Using ci-token to allow easy posting from CI Services 4. This adds predefined variable to GitLab CI build environment: CI_BUILD_STATUS_URL, allowing to easy post status from within build (ex. with code coverage or other metrics). 5. This adds statuses to commit's builds view. 6. The commit's status is calculated taking into account status of all builds and all posted statuses. 7. The commit statuses doesn't trigger notifications. 8. The commit status API introduces two new privileges: `read_commit_statuses` and `create_commit_status`. 9. We still miss a few tests and documentation updates for API and CI. @dzaporozhets @sytses What do you think? See merge request !1530
Diffstat (limited to 'app/views/shared/projects/_project.html.haml')
0 files changed, 0 insertions, 0 deletions