slack_coder
slack_coder copied to clipboard
Slack Bot for watching your Github & CI builds
As a product manager/tech lead I want to know what percent of total Travis PR build failures are caused by flaky tests over a specific time period so I can...
Introduce 3 new PR statuses: - REVIEW requested (when all requested users have not approved/denied) - CHANGES requested (when one or more users have requested changes (i.e. denied)) - READY...
PRs are crashing due to a foreign key constraint error (which is good because that means it cannot delete something it should not). ``` Task #PID started from :"pr-somerepo-12345" terminating...
Some useful ideas for travis integration would be to have some features like: - [x] Parse travis logs to grab failure info - [ ] Make it accessible via web...
The ability to hide a PR from view when it is known to be sitting for a long time. If the staleness feature is fixed, this should also mute the...
See https://www.npmjs.com/package/react-ansi-style Build a react page that fetches the failure log and prints it to the page as a styled ANSI log. Failure logs can be accessed via the `/failure_logs/:id`...
* Fetch logs by filling out `SlackCoder.BuildSystem.CircleCI.build_info/3` and `SlackCoder.BuildSystem.CircleCI.job_log/2`. * (PENDING #35) Cancel builds of old commits
* Fetch logs by filling out `SlackCoder.BuildSystem.Semaphore.build_info/3` and `SlackCoder.BuildSystem.Semaphore.job_log/2`. * (PENDING #35) Cancel builds of old commits
Parse the JEST failure log output See test file checked in at https://github.com/mgwidmann/slack_coder/blob/master/test/support/fixtures/build_system/failed_jest.txt