• Pipeline support for Promoted Builds Plugin

      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

          [JENKINS-36089] Pipeline support for Promoted Builds Plugin

          Greg Smith created issue -
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 172739 ] New: JNJira + In-Review [ 184754 ]
          Jesse Glick made changes -
          Labels New: pipeline
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          quickbrownfox made changes -
          Description Original:
          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
          New: 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 -
          Issue Type Original: New Feature [ 2 ] New: Epic [ 10001 ]
          Oleg Nenashev made changes -
          Epic Name New: Pipeline support for Promoted Builds Plugin
          Oleg Nenashev made changes -
          Epic Child New: JENKINS-35376 [ 171167 ]
          Oleg Nenashev made changes -
          Labels Original: pipeline New: gsoc-2019-project-idea pipeline
          Oleg Nenashev made changes -
          Labels Original: gsoc-2019-project-idea pipeline New: gsoc-2019-project-idea gsoc2019-artifact-promotion-in-pipeline pipeline
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-57634 [ JENKINS-57634 ]

            Unassigned Unassigned
            gregcovertsmith Greg Smith
            Votes:
            153 Vote for this issue
            Watchers:
            169 Start watching this issue

              Created:
              Updated: