Event-driven: Support for CloudEvents specification Jenkins event data reception

[mzmuer]

About #65

I plan to use https://github.com/cloudevents/sdk-go to receive the event data sent by Jenkins-Plugin. Provide a rudimentary scheme to receive events first, and then refine it.

• The CRD is changed by event type, which finally trigger Reconcile
• Afer the apiserver is started, triggered to synchronize the unfinished PieplineRun. Compensates for unexpected loss of event data

[LinuxSuRen]

Please consider the following cases:

• Reuse https://github.com/jenkinsci/cloudevents-plugin
  • It would be great to use https://github.com/cloudevents/sdk-go
• Create a new Jenkins plugin which only sends simple and customized events
  • Don't need to use any SDK

[JohnNiang]

@LinuxSuRen , I guess you misunderstand him. Go SDK for CloudEvents will be used for apiserver only.

BTW, I'd prefer to implement a Jenkins plugin for Pipeline event by ourself due to too many problems in https://github.com/jenkinsci/cloudevents-plugin.

[LinuxSuRen]

IMO, We don't need to use Go SDK for CloudEvents if we want to create a new Jenkins plugin.

[JohnNiang]

@mzmuer , could you please provide more detail on your design? For example, how to update PipelineRun to make it reconcile by controller? Or update labels or annotations?

[mzmuer]

If only sends simple and customized events, detailed event information is not distinguished. That only need is a Webhook API.

@JohnNiang It looks something like this:

• update PipelineRun annotations. similar: event-sync=true or event-sync=Finish
• After Reconcile completes, the annotations are removed and wait to be triggered again

[JohnNiang]

/assign @mzmuer