Group-level Jenkins Integration

Problem to solve

Users have asked to be able to integrate with Jenkins at the organization level, so that an admin would not need to add the Jenkins URL to every project, which is currently the workflow. They would like to have Jenkins integration set up once, and not need to set any configuration for each project.

Further details

GitHub allows this functionality, by utilizing the Jenkinsfile. From https://resources.github.com/articles/practical-guide-to-CI-with-Jenkins-and-GitHub/:

Jenkins scans your entire GitHub organization and creates Pipeline jobs for each repository containing a Jenkinsfile—a text file that defines the process of building, testing, and deploying your project using Jenkins. Immediately after code is checked in or a new pull request is created, Jenkins will execute the Pipeline job and return the status to GitHub indicating whether it failed or succeeded. (Include use cases, benefits, and/or goals)

Proposal

What does success look like, and how can we measure that?

Success looks like a Jenkins configuration that scan the entire GitLab organization, removing the need for project configuration.

The user is looking to automate as much as possible, and reduce the need for manual input within his business's workflow. (If no way to measure success, link to an issue that will implement a way to measure this)

Links / references

Customer requesting:

https://gitlab.my.salesforce.com/00161000016ysnH?srPos=0&srKp=001

Edited Oct 14, 2019 by Patrick Deuley
Assignee Loading
Time tracking Loading