Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #33293
Closed
Open
Issue created Jun 04, 2017 by Pierre Tardy@tardypContributor

Support External CI for Merge Request verification

Description

Gitlab has working support for CI testing via external framework via status API. I am working in integrating the support for merge_request event in the Buildbot CI framework. https://github.com/buildbot/buildbot/pull/3291 The event are properly working, but the results are not properly propagated to the merge request status page.

It is important for larger scale users or people with a more complex pipeline to be able to use external CI framework, and pre-submit CI is an important feature to have.

Looking at the source code of the merge_request page, it looks like the page is directly looking at the gitlab pipeline report, and thus is only integrated with that.

Proposal

I am not exactly sure how to resolve this problem. I think the most simple way to do it is to detect the use of refs/merge-requests/1/head in commit status API, and build a fake merge_request pipeline status in that case.

Edited Jun 04, 2017 by Pierre Tardy
Assignee
Assign to
Time tracking