-
New Feature
-
Resolution: Unresolved
-
Major
To provide a more scalable alternative to the endless requested branch-api customizations such as JENKINS-32396, or the tricks based on JENKINS-30519, it would be useful to have a simple way of calling into scm-api implementations from a Job DSL folder (JENKINS-33275). So you could (for example) easily construct the equivalent of a GitHub organization folder, but from a script loop that could do arbitrary customizations to each, such as setting job properties.
Need to also implement SCMSourceOwner, HeadByItem, etc. so that the branch source knows that a given generated project is associated with a given branch, which is needed for various purposes.
TBD how webhooks should be integrated. The script needs to somehow indicate that changes to a given repository or organization should trigger a regeneration of the folder. May need to create an alternative to SCMTrigger that is keyed off the same criteria that branch-api branch indexing uses, though there are also use cases for traditional SCM polling—it is a little less efficient, but has more configuration options.
For Pipeline projects you could use Jenkinsfile, if SCMBinder and SCMVar were generalized a bit, or something else.
Needs a lot of design work; at this point this is more of a placeholder issue to collect ideas.
- is blocked by
-
JENKINS-33275 Job DSL integration with ComputedFolder
-
- Open
-
- is duplicated by
-
JENKINS-39750 scm should allow configuration in the Jenkinsfile
-
- Resolved
-
-
JENKINS-45727 Allow to add additional items to multibranch pipeline jobs
-
- Resolved
-
- relates to
-
JENKINS-30519 Declarative job properties in multibranch
-
- Resolved
-
-
JENKINS-32396 Option to suppress automatic SCM trigger
-
- Resolved
-
-
JENKINS-35415 Multiple branch projects per repository with different recognizers
-
- Open
-
-
JENKINS-50173 Extension point for marking generated items
-
- Open
-
-
JENKINS-40606 Add ability to perform actions on branch removal
-
- Open
-
-
JENKINS-43749 Support multiple Jenkinsfiles from the same repository
-
- Reopened
-
- links to
- mentioned in
-
Wiki Page Loading...
Use case:
This could be done by allow adding extensions at the GitHub Org Folder level, but that would mean forcing all builds to have a depth of 10, no tags, and submodules turned on. This could cause people to split the GitHub Orgs up just to accommodate Jenkins (which may not be possible, if they are paying for the Orgs, etc.)
An idea is we could change the scm from an Object to the list form (I don't know what it is called) that looks like [$class:GitSCM, extensions: ... ]
I have some code I run in a trusted pipeline via the src/ directory that almost does this...
But this doesn't work because the extensions are missing and it doesn't understand Pull Requests (I don't know why exactly).
This allows getting an "editable" scm object that can have extensions, etc. added to it.