Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36089

Pipeline support for Promoted Builds Plugin

    Details

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

      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

            Activity

            gregcovertsmith Greg Smith created issue -
            rtyler R. Tyler Croy made changes -
            Field Original Value New Value
            Workflow JNJira [ 172739 ] JNJira + In-Review [ 184754 ]
            jglick Jesse Glick made changes -
            Labels pipeline
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            quickbrownfox quickbrownfox made changes -
            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 Oleg Nenashev made changes -
            Issue Type New Feature [ 2 ] Epic [ 10001 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Name Pipeline support for Promoted Builds Plugin
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-35376 [ 171167 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels pipeline gsoc-2019-project-idea pipeline
            oleg_nenashev Oleg Nenashev made changes -
            Labels gsoc-2019-project-idea pipeline gsoc-2019-project-idea gsoc2019-artifact-promotion-in-pipeline pipeline
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-57634 [ JENKINS-57634 ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57839 [ 199797 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57816 [ 199770 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57777 [ 199724 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57637 [ 199567 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57688 [ 199623 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57687 [ 199622 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57921 [ 199893 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57937 [ 199913 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57877 [ 199840 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57689 [ 199624 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57903 [ 199868 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-57861 [ 199823 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-60500 [ 203591 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-60596 [ 203818 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-60597 [ 203819 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels gsoc-2019-project-idea gsoc2019-artifact-promotion-in-pipeline pipeline gsoc-2019-project-idea gsoc2019-artifact-promotion-in-pipeline pipeline roadmap
            oleg_nenashev Oleg Nenashev made changes -
            Status In Progress [ 3 ] Open [ 1 ]

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                gregcovertsmith Greg Smith
              • Votes:
                140 Vote for this issue
                Watchers:
                156 Start watching this issue

                Dates

                • Created:
                  Updated: