Skip to content
GitLab Next
  • Menu
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,097
    • Issues 44,097
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,304
    • Merge requests 1,304
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • #34327
Closed
Open
Created Oct 17, 2019 by Karl Schults@kschults

CI Lint pipeline simulation for tags and non-default branches

Problem to solve

It's very hard to figure out what pipelines will be created and what commands will be run when using pattern matching and variables, especially when using job templates. If, for example, we have pipelines that trigger off matching tags, it's very difficult to test changes to .gitlab-ci.yml without actually pushing the tag and seeing what happens.

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)
  • Devon (DevOps Engineer)
  • Sidney (Systems Administrator)

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->

Proposal

I would like a feature where I can provide a .gitlab-ci.yml file, and then provide various tags, branches, or commits. The tool will display the pipeline of jobs that would be run on the provided tag, and the commands that would be run for each job.

Edited Jan 05, 2022 by Brett Gadberry
Assignee
Assign to
Time tracking