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
  • #1840

Closed
Open
Created Oct 26, 2012 by Administrator@rootOwner

Jenkins integration

Created by: elvanja

Well, it is not really an issue but more of a note. I've put together a Jenkins plugin for Gitlab, that accepts the gitlab payload and builds or queues the project to be built. More about it at https://github.com/elvanja/jenkins-gitlab-hook-plugin Maybe this will help for people in similar situation.

Also, if it is not a problem, you might think about having a system level hook for commits to the projects. The payload already contains the information needed to build the exact project and it would save some time (no need to enter the hook on all the projects). Projects could override or complement that hook too.

Assignee
Assign to
Time tracking