|
|
|
Issue Type:
|
New Feature
|
Assignee:
|
Jesse Glick
|
Components:
|
core |
Created:
|
11/Mar/14 3:27 PM
|
Description:
|
Specialized job types such as are defined in async-job-plugin, branch-api-plugin, or external-monitor-job-plugin do not extend AbstractProject / AbstractBuild because these classes make very specific assumptions about build semantics: that you have a CI job (SCM), an assigned workspace, and so on. Yet without extending those classes you currently have a hard time picking up generic features like
- parameter definitions
- trigger definitions
- manual or REST build causes
- lazy-loading of runs
Those features should be decoupled so that they are available à la carte for other Job / Run types.
|
Project:
|
Jenkins
|
Labels:
|
api
|
Priority:
|
Major
|
Reporter:
|
Jesse Glick
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.