DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Design
How to use the Bot?
Detailed Video : Apache MXNet CI Bot Demo (Youtube Link)
An authorized user can comment on the PR with following 2 commands:
...
- Edit previously made comment
- Should I retrigger the Jenkins?
- Current : Retrigger jenkins
- Delete previously made comment
- How to handle?
- Currently : Ignore
- Error handling
- if bad request (ci trigger fails) how to gracefully handle?
- Currently : No retry. Catch exception.
- Trigger currently running job
- if a job is already running and still verified user retriggers
- Current : retrigger
Upcoming Tasks
- Once approved, configure CI Prod Infra (AWS setup)
- With the Permission of Apache Infra, configure Github Webhooks for public Apache MXNet repository.
Trouble-shooting
- How to fix issues related to the bot?
- First view the logs [Isengard → Prod/Dev account → Cloudwatch Logs]
- Check if Lambda functions are getting triggered
- /send_to_sqs
- /jenkins
- Check if comment author is being verified
- Check if Jenkins Job is being triggered [Verify on Jenkins URL if needed]
- Check if the messages are being posted via Github API
- Send To SQS lambda isn’t triggered
- Check if GitHub WebHook is working correctly
- for Prod account, need Apache Infra team access
- for dev account, tested on my personal fork
- Check on CW Logs for any errors
- Dev account : CW → Log Groups → /aws/lambda/mxnet-ci-bot-test-send
- Jenkins Lambda isn’t triggered
- Problem within Jenkins Lambda function
- Check on CW Logs for any errors
- Dev account : CW → Log Groups → /aws/lambda/mxnet-ci-bot-test-jenkins
- For Jenkins - Github Communication related issues : Refer : Troubleshooting