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

Change delivery-pipeline job property from using section to an optionalBlock



    • Similar Issues:


      Normal convention for Jenkins plugins which contribute a JobProperty to a jobs configuration page is to use an optionalBlock as the top level jelly tag. This is presented to the user as a checkbox, allowing users to hide configuration from plugins they are not using which helps keep a jobs configuration page clean.

      The delivery-pipeline-plugin breaks this convention by using a section as it's top level jelly tag, which presents itself as a new header section.
      The biggest problem with this is, the delivery-pipeline-plugin seems to get rendered in the middle of all the other jobs properties therefore breaking up the page and making the jobs configuration look messy.

      I feel the delivery-pipeline-plugin would look feel/look better if it used the conventional optionalBlock.


          Issue Links


            fluffy88 Seán Dunne created issue -
            fluffy88 Seán Dunne made changes -
            Field Original Value New Value
            Remote Link This issue links to "Pull Request (Web Link)" [ 11915 ]
            patbos Patrik Boström made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            patbos Patrik Boström made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 159721 ] JNJira + In-Review [ 208250 ]


              • Assignee:
                fluffy88 Seán Dunne
                fluffy88 Seán Dunne
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: