-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
I would like to be able to create a multibranch plugin project with the Script Path defined with a wildcard and capture.
As an example I'd like to define the path as something like jenkins/misc/(.*).jenkinsfile and have the generated project name match the capture.
For most projects there are a finite set of build that would be generated. But occasionally projects have a unique build and I'd like them to be able to create those ad-hoc.
The build could be found under <MyOrganizationFolder>/<MyRepo>/develop/<myJenkinsfileName>.
It seems like this could be added to SCMFile.
[JENKINS-69678] Request for wildcard in defining Jenkinsfile paths
Description |
Original:
I would like to be able to create a multibranch plugin project with the {{Script Path}} defined with a wildcard and capture.
As an example I'd like to define the path as something like {{jenkins/misc/(.*).jenkinsfile}} and have the generated project name match the capture. For most projects there are a finite set of build that would be generated. But occasionally projects have a unique build and I'd like them to be able to create those ad-hoc. The build could be found under {{{}<MyOrganizationFolder>/<MyRepo>/develop/<myJenkinsfileName>{}}}. |
New:
I would like to be able to create a multibranch plugin project with the {{Script Path}} defined with a wildcard and capture.
As an example I'd like to define the path as something like {{jenkins/misc/(.*).jenkinsfile}} and have the generated project name match the capture. For most projects there are a finite set of build that would be generated. But occasionally projects have a unique build and I'd like them to be able to create those ad-hoc. The build could be found under {{{}<MyOrganizationFolder>/<MyRepo>/develop/<myJenkinsfileName>{}}}. It seems like this could be added to {{[SCMFile|https://github.com/jenkinsci/scm-api-plugin/blob/df459fad487fe55bd5f59e31b8c6e7ff56bd2228/src/main/java/jenkins/scm/api/SCMFile.java#L150].}} |