-
Epic
-
Resolution: Won't Do
-
Minor
-
None
-
Connected Application
-
See JEP-300
In order to provide a more seamless experience for end-users, and ensure that Jenkins project developers receive useful error and usage telemetry to drive further improvements in Jenkins, Jenkins Essentials must necessarily be viewed as a "Connected" application. This entails some yet-to-be-specified number of server-side applications to coordinate updates, receive and process telemetry, broker 3rd-party service authentications, relay webhooks, etc.
[JENKINS-49846] Maintain connectivity to a service layer for providing a more seamless experience.
Description | Original: See [JEP-300|https://github.com/jenkinsci/jep/tree/master/jep/300#connected] |
New:
See [JEP-300|https://github.com/jenkinsci/jep/tree/master/jep/300#connected] {quote} In order to provide a more seamless experience for end-users, and ensure that Jenkins project developers receive useful error and usage telemetry to drive further improvements in Jenkins, Jenkins Essentials must necessarily be viewed as a "Connected" application. This entails some yet-to-be-specified number of server-side applications to coordinate updates, receive and process telemetry, broker 3rd-party service authentications, relay webhooks, etc. {quote} |
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|
Epic Child |
New:
|