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

Parameterized downstream/upstream project name parsing for Delivery Pipeline Plugin

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • * Jenkins 2 LTS branch
      Other relevant plugins:
      * EZ Templates Plugin

      When defining Post-build Action "Build other projects", I want to be able to use parameters defined in Parameters section, so that I can avoid hardcoding, and more importantly be able to visualize a delivery pipeline using template jobs.

      Without this, "Build other projects" correctly interpolates the parameter, and triggers the downstream job, but the Delivery Pipeline view is unable to visualize this relation.

      To put things into context, here is a use case:

      • There are build and qa template jobs (using EZ Templates Plugin).
      • Parameters are implementation specific, whereas many other things are inherited from templates.
      • There are multiple projects using the same build and qa templates for building and deploying to qa respectively.
      • "Build other projects" triggers qa job based on project name, such as "${projectName}-qa". This is where delivery pipeline plugin is unable to parse the resultant downstream job name, and display it on the view.

            patbos Patrik Boström
            djan Can Yildiz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: