Details
-
Type:
Improvement
-
Status: Reopened (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: workflow-multibranch-plugin
-
Labels:None
-
Similar Issues:
Description
This would support scenarios where different "configurations" of a pipeline cannot share the same Jenkinsfile.
If I had multiple Jenkinsfiles... repository github.com/apple/swift
/Package.jenkinsfile /Incremental.jenkinsfile /Incremental-RA.jenkinsfile /Assert.jenkinsfile /src/…
I would like to create multibranch Pipelines for each so I have the resulting structure:
/Apple /Apple/Swift - Package /Apple/Swift - Incremental /Apple/Swift - Incremental-RA /Apple/Swfit - Assert
Note that in this example I have an organization folder for github.com/apple and it is creating multiple multibranch pipelines for each Jenkinsfile discovered in each repository.
I have written up examples and use cases in this doc
Attachments
Issue Links
- duplicates
-
JENKINS-35415 Multiple branch projects per repository with different recognizers
-
- Open
-
- is duplicated by
-
JENKINS-46251 Need to get Jenkinsfiles which can use more than 1 project in the same repo
-
- Resolved
-
-
JENKINS-45273 Pipeline Multibranch - Add the possibility to use a Jenkinsfile from other SCM
-
- Resolved
-
- relates to
-
JENKINS-37220 Job DSL analogue of multibranch projects & organization folders
-
- Open
-
- links to
- mentioned in
-
Wiki Page Loading...
Tzach Yarimi to clarify, we had different multibranch pipeline job for different component. So what service does is create a new multibranch pipeline job when it detects a new component added to the repository. The new job will be configured to use the Jenkinsfile specific of that new component.
If the job already exists, it will check if the branch is already registered otherwise it will update the job config to add a new branch and start the scanning process to make the branch job available. Once the branch job is available, the service will trigger the build of that.
Unfortunately I could not share the code.