CI/CD ideas #16
Replies: 1 comment
-
Thanks for starting this discussion @iMacTia . Since accountability and ownership is such a fundamental component to effectively managing a large distributed team, there are endless ways to use this. Here is a big laundry list of some of the ways that we use it at Gusto. Test segmentationWhen we run our front-end tests, we identify the owner of each file using General code ownership validations
Packwerk integrationsWe use this with packwerk to identify the team that owns a packwerk package to help direct users to the right team when packwerk fails Logging/monitoring/observabilityWe use Flaky test reportingWhen a test flakes, we identify the owner with code ownership and report it to the team's slack channel (as specified in ther team YML). PagingWe use code ownership to identify the team to page when something goes wrong. Metric segmentationWhen we have metrics (e.g. sorbet/typescript stats/modularization stats/etc.), we use CodeOwnership to segment so teams can track progress individually. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
I bumped into this gem and it looks really great!
There are all sorts of applications for it, but I'm really curious to hear how you currently use it in your CI/CD environments.
Suggestions, examples, and ideas are all welcome: how are you currently using this gem to automate your development process?
Here is a list of interesting applications that I'm not yet sure how to implement:
CODEOWNERS
file up-to-datefor_stacktrace
with error tracking tools to automatically assign owners to errorsBeta Was this translation helpful? Give feedback.
All reactions