Category |
Analysis |
Actions/Impact |
Configuration Issue |
These issues can be resolved by changing system settings or by modifying a JVM system property. |
No upgrade of Jenkins core or a plugin is required to resolve these issues. |
External Issue |
These issues can be resolved by changing an external system; for example, a bug in an SCM server may cause it to send malformed data to Jenkins. |
No change to Jenkins is required to resolve these issues. |
Jenkins Core Issue |
These issues can only be resolved by a code change in the Jenkins core. |
CloudBees first priority is to try to make the fix available in the next release of the line the customer is running. If the fix is ineligible for inclusion in that release line (either for technical reasons, such as requiring a new feature only available in a newer line, or resulting from the risk assessment of the fix), the customer may be required to upgrade to a newer release line where that fix is eligible. In certain cases, it may be possible to provide a hotfix/patch in the form of a plugin that may mitigate the issue; such hot fix plugins are only developed for serious issues where the approach is technically feasible. |
Plugin Issue |
These issues can only be resolved by a code change in the plugin(s). |
CloudBees first priority is to make the fix available in the next release of the plugin(s).
|
Interaction Issue Between the Jenkins Core and Plugin(s) |
This is a combination of the previous two categories where the fix is required both in the Jenkins core and a corresponding plugin. |
Typically, these issues can only be resolved in the Jenkins community weekly line and will only become available in older lines as they overtake the weekly version containing the fix. Unfortunately, due to the cross-system nature of these issues, resolution will generally require the customer to change the core version of Jenkins and upgrade plugins. |
Comments
0 comments
Please sign in to leave a comment.