Topic on Talk:Platform Engineering Team/Event Platform Value Stream/Use case: Event Platform SDLC practices

On the topic of existing workflows in our Gerrit/Zuul/Jenkins based system, you might want to have a look at the documentation for PipelineLib. PipelineLib depends on Jenkins so we won't be using it in its current state from GitLab, but we do plan to provide a GitLab CI library that will provide the same functions (albeit using native GitLab CI configuration) as well as tooling for easy migration.

Thanks for the pointer @DDuvall (WMF).

I've read through https://wikitech.wikimedia.org/wiki/PipelineLib/Concepts, and I wanted to understand the following points a bit better:

1. What is the time horizon for a Gitlab-compatible PipelineLib?
2. Will it support deployments to environments other than production k8s (e.g. yarn, DSE cluster)?
3. The doc says We only support microservices. What's the definition of microservice in this context? Our value stream will develop artifacts that are not microservices (e.g. data pipelines, flink jobs), but that will adhere to deployment-charts norms for k8s targets. Would these fit PipelineLib use cases?

In general, how would you advise we proceed with new Gitlab projects? Is it safe to start building workflows around current Gitlab CI capabilities (e.g. by piggybacking on efforts like https://gitlab.wikimedia.org/repos/data-engineering/workflow_utils/-/tree/main/gitlab_ci_templates).