Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #231352
Closed
Open
Issue created Jul 23, 2020 by Fabio Pitino@fabiopitino2️⃣Maintainer

Create CI Lint API endpoint scoped to project

In !37134 (merged) we expanded the CI Lint to use a dry run mode which goes deeper in the pipeline creation stack, providing a simulation of the actual pipeline creation.

The dry run mode was implemented only for Projects::Ci::LintsController#create while the API endpoint still uses the legacy method via YamlProcessor. Converting the existing API endpoint to use dry run is not possible because it's project agnostic. The dry run is project-aware.

To solve this problem we could introduce a new API endpoint scoped to projects: POST v4/projects/:id/ci/lint which would have dry run on by default.

This endpoint should return:

{ 
  status: 'failed', # or success
  errors: [ ... ],
  warnings: [ ... ],
  jobs: [ ... ] # if status: success
}
Edited Jul 23, 2020 by Fabio Pitino
Assignee
Assign to
Time tracking