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

Promotion name needs to be a parameter to avoid duplication

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • promoted-builds-plugin
    • None
    • Linux 64

      With multiple promotion options that differ only by one token, which is the same as the promotion name itself, it would be great to be able to create one promotion block that is optionally executed for a range of promotions.

      IOW, Say I have a promotion names P1. It does things with files/P1/...

      Then I need to create other promotions, P2, P3, etc, that need to do the exact same thing relative to the promotion name, files/P2/... and files/P3/... .

      A better option would be to define the promotion block once, then define the promotion names for which it could be executed.

      Currently I have to replicate the entire promotion block, which is very non-DRY when testflight is involved as there's a lot of boilerplate that goes into every promotion block.

            Unassigned Unassigned
            bedge Bruce Edge
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: