-
New Feature
-
Resolution: Fixed
-
Major
-
None
In multibranch pipeline and Github organization folder the name Jenkinsfile is hard-coded and always looks for the top level folder.
It would be useful to have the option to search other specified files (even located in subfolders) to face cases like:
- having multiple repo-scanners managed by one project that create different pipelines from the same repo (they do different things, executing on different schedules)
- some git repos requires a project layout that forbids all root-level files with some exceptions
- is duplicated by
-
JENKINS-42265 Allow multibranch pipelines to analyze sub-directories for Jenkinsfile
-
- Closed
-
-
JENKINS-38147 Allow per-job Parameters for Multi-Branch
-
- Resolved
-
-
JENKINS-40634 allow suffix ".groovy" for Jenkinsfile
-
- Closed
-
- is related to
-
JENKINS-39861 Jenkinsfile path of Multibranch pipeline
-
- Closed
-
- relates to
-
JENKINS-35415 Multiple branch projects per repository with different recognizers
-
- Open
-
- mentioned in
-
Wiki Page Loading...
[JENKINS-34561] Allow to detect different Jenkinsfile filenames
Description |
Original:
In multibranch workflows and Github organization folder the name "Jenkinsfile" is hard-coded and always looks for the top level folder. It would be useful to have the option to search other specified files (even located in subfolders) to face cases like: * having multiple repo-scanners managed by one project that create different pipelines from the same repo (they do different things, executing on different schedules) * some git repos requires a project layout that forbids all root-level files with some exceptions |
New:
In multibranch pipeline and Github organization folder the name "Jenkinsfile" is hard-coded and always looks for the top level folder. It would be useful to have the option to search other specified files (even located in subfolders) to face cases like: * having multiple repo-scanners managed by one project that create different pipelines from the same repo (they do different things, executing on different schedules) * some git repos requires a project layout that forbids all root-level files with some exceptions |
Description |
Original:
In multibranch pipeline and Github organization folder the name "Jenkinsfile" is hard-coded and always looks for the top level folder. It would be useful to have the option to search other specified files (even located in subfolders) to face cases like: * having multiple repo-scanners managed by one project that create different pipelines from the same repo (they do different things, executing on different schedules) * some git repos requires a project layout that forbids all root-level files with some exceptions |
New:
In multibranch pipeline and Github organization folder the name {{Jenkinsfile}} is hard-coded and always looks for the top level folder. It would be useful to have the option to search other specified files (even located in subfolders) to face cases like: * having multiple repo-scanners managed by one project that create different pipelines from the same repo (they do different things, executing on different schedules) * some git repos requires a project layout that forbids all root-level files with some exceptions |
Component/s | New: workflow-plugin [ 18820 ] | |
Component/s | Original: multi-branch-project-plugin [ 21127 ] |
Assignee | Original: Jesse Glick [ jglick ] | New: Manuel Recena Soto [ recena ] |
Component/s | Original: github-branch-source-plugin [ 20858 ] | |
Assignee | Original: Manuel Recena Soto [ recena ] | New: Jesse Glick [ jglick ] |
Labels | Original: multibranch pipeline | New: multibranch |
Workflow | Original: JNJira [ 170708 ] | New: JNJira + In-Review [ 184005 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Component/s | New: workflow-multibranch-plugin [ 21465 ] | |
Component/s | Original: pipeline [ 21692 ] |