-
Story
-
Resolution: Duplicate
-
Major
In Scope
Create a new multibranch job given sufficient parameters:
- Take an "organisation" name
- Take a type of branchSource (could be git, github, bitbucket)
- Take a pattern (ant glob or regex) for building branches that match the pattern (includes)
- If plain Git:
- take repo url
- take optional credential name field
- If github/bitbucket
- take server URL (e.g. https://github.com or https://github.internal.corp/)
- take owner and repository name
- take optional api endpoint (in the case of bitbucket, optional ssh port)
- take optional credentials name field
Future extensibility
- As there are other branch source and repo types, the api should be able to cope with config specific to different branch sources, avoid assuming the world is git
Out of scope:
- Add multiple branch sources
- Defining what the credentials are (its just a name that is referred to, assuming credentials are already set up).
- duplicates
-
-
- Resolved
-
- relates to
-
JENKINS-35872 API for editing pipeline settings
-
- Resolved
-
[JENKINS-35787] API to create a new multibranch pipeline
| Epic Link | New: UX-183 [ 25894 ] |
| Sprint | New: 1.0-m8 [ 46 ] |
| Rank | New: Ranked higher |
| Description |
Original:
In Scope Create a new multibranch job given sufficient parameters: * Take a type of branchSource (could be git, github, bitbucket) * Take a pattern (ant glob or regex) for building branches that match the pattern (includes) * If plain Git: ** take repo url ** take optional credential name field * If github/bitbucket ** take owner and repository name ** take optional api endpoint (in the case of bitbucket, optional ssh port) ** take optional credentials name field Future extensibility * As there are other branch source and repo types, the api should be able to cope with config specific to different branch sources, avoid assuming the world is git Out of scope: * Add multiple branch sources * Defining what the credentials are (its just a name that is referred to, assuming credentials are already set up). |
New:
In Scope Create a new multibranch job given sufficient parameters: * Take an "organisation" name (default: jenkins) * Take a type of branchSource (could be git, github, bitbucket) * Take a pattern (ant glob or regex) for building branches that match the pattern (includes) * If plain Git: ** take repo url ** take optional credential name field * If github/bitbucket ** take owner and repository name ** take optional api endpoint (in the case of bitbucket, optional ssh port) ** take optional credentials name field Future extensibility * As there are other branch source and repo types, the api should be able to cope with config specific to different branch sources, avoid assuming the world is git Out of scope: * Add multiple branch sources * Defining what the credentials are (its just a name that is referred to, assuming credentials are already set up). |
| Sprint | Original: 1.0-m8 [ 46 ] |
| Sprint | New: 1.0-japan-m9 [ 41 ] |
| Rank | New: Ranked higher |
jdumay as mentioned in #
UX-534- do we want to stick to git/github/bitbucket or include other SCM branch sources? (svn, mercurial) - given Jenkins can do them?