Tags: commercetools/telefonistka
Tags
Add support for retriggering via PR comment (#115) * Add support for retriggering via PR comment * fixup! Add support for retriggering via PR comment * fixup! Add support for retriggering via PR comment * Make handleChangedPREvent able to handle comment event Instead of passing in the PullRequestEvent, the signature is changed to accept the only used attributes of PR number and the list of labels. This allows it to be called when receiving a IssueCommentEvent, triggered from a "retrigger"-comment. * Move panic handler A triggering comment can now potentially cause a panic so the handler is moved to cover such cases, avoiding a crashed server if there are bugs. * Refactor getting PR ref and SHA The only use of GetRef and GetSHA is in the comment event handler. This refactors its use in an effort to simplify; the comment handler instead fetches the PR object directly once, and aborts if the issue is not linked to a PR. It then sets the ref and SHA based on the returned object values. * Trim off leading and trailing space * Lint * Log when bailing
Generate argoCD diff comments with Go code instead of GoTemplate (#72) * Initial commit for avoiding goTemplate in PR comment * Avoid displaying health/status warnings for "temp" apps. * Add tests * Tune comment size test limit to match new data in diff_comment_data_test.json" * Avoid linting the testdata markdown file (for now) Co-authored-by: Hannes Gustafsson <hannes.gustafsson@commercetools.com>
Support custom generator (#46) * argocd: guard against missing Git configuration If the found ApplicationSet contains no Git configuration Telefonistka crashes. Guarding against the missing configuration should avoid the crash. * Make test parallel * Use component path that works in lab * Support custom generator Adds support for custom generator as long as the generator has an input parameter named "path". Note that it would probably be advisable to make it configurable, but this is left as a future exercise for the reader.
monitoring PR handling failures. (#42) Instrument PR handling failures. We track both explicit failures with pr_handle_failures_total And cases where telefonistka commit status check is left in "pending" state (because Telefonistka exploded while handling that event ) Co-authored-by: Yazdan Mohammadi <yazdan.mohammadi@commercetools.com>
PreviousNext