![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Seán Dunne
|
|
Components:
|
delivery-pipeline-plugin |
|
Created:
|
22/Nov/14 11:10 AM
|
|
Description:
|
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.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Seán Dunne
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
