Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #7047

Closed
Open
Created May 30, 2014 by Administrator@rootOwner

CI Status Not Allowing Unknown

Created by: bassrock

Hi,

I am developing a plugin for a new ci service and while going through how Gitlab, connects to GItlab CI I see it allows an unknown state. This however is not allowed in the page that gets displayed to the user in merge requests and instead the user sees an unable to connect to CI error, when really it should be an "Unallowed state" error.

Either way in this section: https://github.com/gitlabhq/gitlabhq/blob/7c6a58a756cc3bff78a6d0a0ca8abfe9b2c147da/app/assets/javascripts/merge_request.js.coffee#L91

It should allow an unknown state since Gitlab CI allows it.

Assignee
Assign to
Time tracking