[JENKINS-36089] Pipeline support for Promoted Builds Plugin - Jenkins Jira

XML

Word

Printable

Details

Type: Epic
Status: Open (View Workflow)
Priority: Major
Resolution: Unresolved
Component/s: promoted-builds-plugin
Labels:

Epic Name:
Pipeline support for Promoted Builds Plugin
Similar Issues:

Show

Description

This enhancement request is for the Promoted Builds plugin to support Jenkins' 2.X style Pipelines.

Pipelines are the new paradigm that Jenkins 2.X is promoting heavily – with its ability to define the build process in code, automatic build discovery, and great integration with repository systems for automatic build / testing of pull requests.

There are many places within the new Pipeline style where the Promoted Plugin could be used to great effect:

builds could dynamically https://issues.jenkins-ci.org/browse/JENKINS-36089#promote and save artifacts, pushing them into other pipeline jobs
Users could manually promote pipeline builds that have been through some kind of QA process
Permalinks provided by the Promoted Builds plugin could be used in pipeline builds

Basically, the same vast number of use cases that the Promoted Build Plugin provides today could be taken advantage of by builds defined via the Pipeline API and Jenkinsfile build definitions.

Reference here for the API changes that are required for a plugin to be available in a Pipeline build:
https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

Original reference bug:
https://issues.jenkins-ci.org/browse/JENKINS-35376

Attachments

Issue Links

relates to

JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)

Resolved

Activity

Ascending order - Click to sort in descending order

Greg Smith created issue - 2016-06-20 15:59

R. Tyler Croy made changes - 2016-07-25 23:52

Field	Original Value	New Value
Workflow	JNJira [ 172739 ]	JNJira + In-Review [ 184754 ]

Jesse Glick made changes - 2016-10-27 18:13

Labels

pipeline

Oleg Nenashev made changes - 2016-12-20 08:26

Assignee

Oleg Nenashev [ oleg_nenashev ]

quickbrownfox made changes - 2017-01-27 17:12

Description

This enhancement request is for the Promoted Builds plugin to support Jenkins' 2.X style Pipelines.

Pipelines are the new paradigm that Jenkins 2.X is promoting heavily -- with its ability to define the build process in code, automatic build discovery, and great integration with repository systems for automatic build / testing of pull requests.

There are many places within the new Pipeline style where the Promoted Plugin could be used to great effect:
- builds could dynamically promote and save artifacts, pushing them into other pipeline jobs
- Users could manually promote pipeline builds that have been through some kind of QA process
- Permalinks provided by the Promoted Builds plugin could be used in pipeline builds

Basically, the same vast number of use cases that the Promoted Build Plugin provides today could be taken advantage of by builds defined via the Pipeline API and Jenkinsfile build definitions.

Reference here for the API changes that are required for a plugin to be available in a Pipeline build:
https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

Original reference bug:
https://issues.jenkins-ci.org/browse/JENKINS-35376

This enhancement request is for the Promoted Builds plugin to support Jenkins' 2.X style Pipelines.

Pipelines are the new paradigm that Jenkins 2.X is promoting heavily -- with its ability to define the build process in code, automatic build discovery, and great integration with repository systems for automatic build / testing of pull requests.

There are many places within the new Pipeline style where the Promoted Plugin could be used to great effect:
- builds could dynamically https://issues.jenkins-ci.org/browse/JENKINS-36089#promote and save artifacts, pushing them into other pipeline jobs
- Users could manually promote pipeline builds that have been through some kind of QA process
- Permalinks provided by the Promoted Builds plugin could be used in pipeline builds

Basically, the same vast number of use cases that the Promoted Build Plugin provides today could be taken advantage of by builds defined via the Pipeline API and Jenkinsfile build definitions.

Reference here for the API changes that are required for a plugin to be available in a Pipeline build:
https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

Original reference bug:
https://issues.jenkins-ci.org/browse/JENKINS-35376

Oleg Nenashev made changes - 2017-06-13 08:01

Issue Type

New Feature [ 2 ]

Epic [ 10001 ]

Oleg Nenashev made changes - 2017-06-13 08:02

Epic Name

Pipeline support for Promoted Builds Plugin

Oleg Nenashev made changes - 2017-06-13 08:02

Epic Child

JENKINS-35376 [ 171167 ]

Oleg Nenashev made changes - 2018-12-30 12:05

Labels

pipeline

gsoc-2019-project-idea pipeline

Oleg Nenashev made changes - 2019-05-13 09:33

Labels

gsoc-2019-project-idea pipeline

gsoc-2019-project-idea gsoc2019-artifact-promotion-in-pipeline pipeline

Jesse Glick made changes - 2019-05-30 01:32

Link

This issue relates to ~~JENKINS-57634~~ [ ~~JENKINS-57634~~ ]

Oleg Nenashev made changes - 2019-12-16 12:25

Assignee

Oleg Nenashev [ oleg_nenashev ]

Oleg Nenashev made changes - 2019-12-16 12:25

Status

Open [ 1 ]

In Progress [ 3 ]