-
Task
-
Resolution: Won't Fix
-
Major
In Scope
Modify for any job type:
- enable or disable the job
- change it's name
- look up if its enabled or disabled
- pass an "organization" name with every request
Modify for multi-branch pipelines:
- Enable/disable automatically building branches
- Set a pattern (ant glob or regex) for building branches that match the pattern
- e.g. feature/* will only build branches starting with the feature/ prefix.
- Enable/disable automatically building pull requests
- Enable/disable building Pull Requests originating from forked repositories
- Use case: we only build PRs who's branches are in the same source repo for security purposes
- change credentials used
- change repo details (url, or owner/name in the case of github/bitbucket)
- Change api endpoint (or bitbucket ssh port)
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
- Changing the job type
- Deleting the job
- Create a freestyle job type
- Changing the branch source type from, say, github to bitbucket
- blocks
-
JENKINS-35790 Developer wants to change some pipeline settings
-
- Resolved
-
- relates to
-
JENKINS-35782 API to list available repositories for an owner
-
- Resolved
-
-
JENKINS-35787 API to create a new multibranch pipeline
-
- Resolved
-
[JENKINS-35872] API for editing pipeline settings
Sprint | New: 1.0-m8 [ 46 ] |
Rank | New: Ranked higher |
Labels | New: api |
Attachment | New: Pipline Config - Branching tab.png [ 17317 ] | |
Attachment | New: Pipline Config - General tab.png [ 17316 ] |
Summary | Original: API for changing pipeline settings | New: API for creating new multibranch pipeline or changing settings |
Summary | Original: API for creating new multibranch pipeline or changing settings | New: API for creating new multibranch pipeline and changing settings |
Description |
Original:
In Scope For any job: * enable or disable the job * change is name * look up if its enabled or disabled For multi-branch pipelines: * Enable/disable automatically building branches * Set a pattern (ant glob or regex) for building branches that match the pattern ** e.g. {{feature/*}} will only build branches starting with the {{feature/}} prefix. * Enable/disable automatically building pull requests * Enable/disable building Pull Requests originating from forked repositories ** Use case: we only build PRs who's branches are in the same source repo for security purposes |
New:
In Scope Modify for any job type: * enable or disable the job * change is name * look up if its enabled or disabled Create a multi-branch pipeline: * Take Modify for multi-branch pipelines: * Enable/disable automatically building branches * Set a pattern (ant glob or regex) for building branches that match the pattern ** e.g. {{feature/*}} will only build branches starting with the {{feature/}} prefix. * Enable/disable automatically building pull requests * Enable/disable building Pull Requests originating from forked repositories ** Use case: we only build PRs who's branches are in the same source repo for security purposes Out of scope: * Add multiple branch sources * Changing the branch source "type" * Changing the job type * Deleting the job |
Summary | Original: API for creating new multibranch pipeline and changing settings | New: API for creating and editing new multibranch pipeline and changing settings |
Description |
Original:
In Scope Modify for any job type: * enable or disable the job * change is name * look up if its enabled or disabled Create a multi-branch pipeline: * Take Modify for multi-branch pipelines: * Enable/disable automatically building branches * Set a pattern (ant glob or regex) for building branches that match the pattern ** e.g. {{feature/*}} will only build branches starting with the {{feature/}} prefix. * Enable/disable automatically building pull requests * Enable/disable building Pull Requests originating from forked repositories ** Use case: we only build PRs who's branches are in the same source repo for security purposes Out of scope: * Add multiple branch sources * Changing the branch source "type" * Changing the job type * Deleting the job |
New:
In Scope Modify for any job type: * enable or disable the job * change it's name * look up if its enabled or disabled Create a multi-branch pipeline, by taking the following (minimal) params: * * 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 field Modify for multi-branch pipelines: * Enable/disable automatically building branches * Set a pattern (ant glob or regex) for building branches that match the pattern ** e.g. {{feature/*}} will only build branches starting with the {{feature/}} prefix. * Enable/disable automatically building pull requests * Enable/disable building Pull Requests originating from forked repositories ** Use case: we only build PRs who's branches are in the same source repo for security purposes * change credentials used * change repo details (url, or owner/name in the case of github/bitbucket) * Change api endpoint (or bitbucket ssh port) 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 * Changing the branch source "type" * Changing the job type * Deleting the job * Create a freestyle job type |