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

View Jenkins Pipelines as a job in standard Delivery Pipeline View

      As the "Build dependancies" and "Delivery Pipeline configuration" are available in a jenkins pipeline job or in simples jobs, it could be simple to display jenkins pipeline job like standards jobs in a delivery pipeline view and will permit  to create visibles dependencies between manual jobs and pipeline jobs.

      The result, to have : 

      • all delivery pipeline advantages
      • all jenkins pipeline advantages

       

      Thanks for this great plugin

          [JENKINS-50587] View Jenkins Pipelines as a job in standard Delivery Pipeline View

          Tommy Tynjä added a comment -

          ndm Glad to hear that you like the plugin! Thanks for an interesting feature proposal. If it could be accommodated in the plugin it sure could bring user value. In order to realize this in the near future it would require effort by a community contributor.

          Tommy Tynjä added a comment - ndm Glad to hear that you like the plugin! Thanks for an interesting feature proposal. If it could be accommodated in the plugin it sure could bring user value. In order to realize this in the near future it would require effort by a community contributor.

          Tommy Tynjä added a comment -

          The DeliveryPipelineView that visualizes downstream dependencies using traditional Jenkins jobs is built around the Jenkins AbstractProject abstraction. Jenkins pipelines are modeled with the WorkflowJob class which does not extend the AbstractProject. The common abstraction would be a hudson.model.Job. This feature is possible to implement, however it would require a whole lot of changes to make use of the Job abstraction instead in the DeliveryPipelineView.

          Tommy Tynjä added a comment - The DeliveryPipelineView that visualizes downstream dependencies using traditional Jenkins jobs is built around the Jenkins AbstractProject abstraction. Jenkins pipelines are modeled with the WorkflowJob class which does not extend the AbstractProject. The common abstraction would be a hudson.model.Job. This feature is possible to implement, however it would require a whole lot of changes to make use of the Job abstraction instead in the DeliveryPipelineView.

          Hubert S added a comment -

          This is a tricky spot for the pipelines, I find myself needing to constrain all the jobs to be AbstractProject or Workflow job just to benefit from this great plugin! Tough in this Jenkins transition where it seems like Pipelines vs Traditional jobs are split 50/50 in desires/fit. 

          I'm surprised this Jira doesn't have that much action. How is everyone coping? Delivery pipelines are a common thing, and I'm not sure a single Jenkins Pipeline can accommodate it all in present state, and sometimes job separation is needed.

          Hubert S added a comment - This is a tricky spot for the pipelines, I find myself needing to constrain all the jobs to be AbstractProject or Workflow job just to benefit from this great plugin! Tough in this Jenkins transition where it seems like Pipelines vs Traditional jobs are split 50/50 in desires/fit.  I'm surprised this Jira doesn't have that much action. How is everyone coping? Delivery pipelines are a common thing, and I'm not sure a single Jenkins Pipeline can accommodate it all in present state, and sometimes job separation is needed.

            patbos Patrik Boström
            ndm Nicolas de Marqué
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: