Is your feature request related to a problem? Please describe.
Werft is a great tool to run super-specialized CI/CD pipelines. However, werft has its own singularities that are not widely spread, e.g. log slices and phases, and writing a job that follows werft standards can be quite difficult at the beginning.
Additionally, useful additions that are not related to the core logic of a job are often forgotten (e.g. measuring job/phase duration, setting up slack notifications, instrumenting tracing and/or pushgateway metrics) and that could be added to the supporting libraries.
Describe the solution you'd like
We could create libraries that specialize in giving support to developers who want to create/maintain werft jobs.
Starting with typescript and golang.
Describe alternatives you've considered
gitpod-io/gitpod has an okayish library that helps with logs under slices, but that's it. We'd need to replicate this code in other repositories if we'd like to use it.
Is your feature request related to a problem? Please describe.
Werft is a great tool to run super-specialized CI/CD pipelines. However, werft has its own singularities that are not widely spread, e.g. log slices and phases, and writing a job that follows werft standards can be quite difficult at the beginning.
Additionally, useful additions that are not related to the core logic of a job are often forgotten (e.g. measuring job/phase duration, setting up slack notifications, instrumenting tracing and/or pushgateway metrics) and that could be added to the supporting libraries.
Describe the solution you'd like
We could create libraries that specialize in giving support to developers who want to create/maintain werft jobs.
Starting with typescript and golang.
Describe alternatives you've considered
gitpod-io/gitpod has an okayish library that helps with logs under slices, but that's it. We'd need to replicate this code in other repositories if we'd like to use it.