Skip to content

Draft: [DO NOT MERGE] Spike tracking metric for CI keyword junit

Albert requested to merge alberts-spike-ci-config-track-usage into master

Spike to send metric for CI keyword usages.

There are requirements to track usage of various CI keywords per user, such as #339720 (closed), #339721 (closed).

To do so, we could collect the event names that need to be sent to UsageData as the CI YAML is processed.

After the event names are collected, we could emit the metric events. However, due to performance concerns on pipeline creation, we should not emit the metric events until the pipeline has been created and persisted.

I am looking for comments on:

  • feasibility of the approach
  • potential performance impact on pipeline creation
Edited by Albert

Merge request reports