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
  • #27983
Closed
Open
Issue created Apr 10, 2019 by Balasankar 'Balu' C@balasankarcDeveloper

Add support for providing pipeline variables via git push options

Problem to solve

In omnibus-gitlab pipelines, the decision of whether a CE package is to be built or an EE one is taken by several factors. One override for that is the ee variable, upon the presence of which, an EE package is built. More than often, we need to build an EE package for testing, and the current workflow involves either polluting the .gitlab-ci.yml file with ee variable, or going to the UI and manually running a pipeline with ee variable set. If the commit doesn't have any CI skip directive, this means we are essentially running an additional unwanted pipeline.

Proposal

Make it possible to pass CI variables using git's push options. This way, while pushing the code to the repo we can specify the variables to be used in the pipeline, thus not polluting the CI config file, or make the trouble of going to the UI to start a pipeline.

Intended users

Developers

Assignee
Assign to
Time tracking