-
Story
-
Resolution: Won't Fix
-
Major
contingency:: should Jenkinsfile's appear to be too low level for common build tasks, if plumber is not available, we are able to ship some pre-made global libraries for common tasks.
Including
- simple notifying via hipchat/slack (without having to write scripts)
- building inside docker
- maven build and archive of test results
- publishing docker images
- deploying to common targets
BlueOcean already has a dependency on pipeline, so these can be encapsulated in a plugin and shipped with it.
How this is done is described here: https://jenkins.io/blog/2016/04/21/dsl-plugins/
(interested if imeredith has some suggestions of what to include out of the box).
This helps the UX for new users of Jenkins.
When a user creates a new pipeline (ie selects a repo) if there is no Jenkinsfile, we can offer these as samples to use.
[JENKINS-35844] (contingency) Provide included Global DSL (global var) for common pipelines
Epic Link | New: UX-137 [ 25631 ] |
Assignee | New: Michael Neale [ deactivated user ] |
Description |
Original:
contingency:: should Jenkinsfile's appear to be too low level for common build tasks, if plumber is not available, we are able to ship some pre-made global libraries for common tasks. Including * simple notifying via hipchat/slack (without having to write scripts) * building inside docker * maven build and archive of test results * publishing docker images * deploying to common targets BlueOcean already has a dependency on pipeline, so these can be encapsulated in a plugin and shipped with it. How this is done is described here: https://jenkins.io/blog/2016/04/21/dsl-plugins/ (interested if [~imeredith] has some suggestions of what to include out of the box). This helps the UX for new users of Jenkins. |
New:
contingency:: should Jenkinsfile's appear to be too low level for common build tasks, if plumber is not available, we are able to ship some pre-made global libraries for common tasks. Including * simple notifying via hipchat/slack (without having to write scripts) * building inside docker * maven build and archive of test results * publishing docker images * deploying to common targets BlueOcean already has a dependency on pipeline, so these can be encapsulated in a plugin and shipped with it. How this is done is described here: https://jenkins.io/blog/2016/04/21/dsl-plugins/ (interested if [~imeredith] has some suggestions of what to include out of the box). This helps the UX for new users of Jenkins. When a user creates a new pipeline (ie selects a repo) if there is no Jenkinsfile, we can offer these as samples to use. |
Rank | New: Ranked higher |
Rank | New: Ranked lower |
Project Import | New: Tue Jun 14 12:50:41 JST 2016 [ 1465876241198 ] |
Project Import | New: Wed Jun 15 02:53:18 UTC 2016 [ 1465959198925 ] |
Labels | New: blueocean-imported |
Component/s | New: blueocean-plugin [ 21481 ] | |
Key |
Original:
|
New:
|
Workflow | Original: Product Backlog April 2016 V2 [ 172159 ] | New: JNJira [ 172464 ] |
Project | Original: User Experience [ 10600 ] | New: Jenkins [ 10172 ] |
Status | Original: To Do [ 10003 ] | New: Open [ 1 ] |
Assignee | Original: Michael Neale [ deactivated user ] |