Page History

...

• 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

1. Once approved, configure CI Prod Infra (AWS setup)
2. With the Permission of Apache Infra, configure Github Webhooks for public Apache MXNet repository.

Trouble-shooting

1. How to fix issues related to the bot?
1. First view the logs [Isengard → Prod/Dev account → Cloudwatch Logs]
2. Check if Lambda functions are getting triggered
1. /send_to_sqs
2. /jenkins
3. Check if comment author is being verified
4. Check if Jenkins Job is being triggered [Verify on Jenkins URL if needed]
5. Check if the messages are being posted via Github API
2. Send To SQS lambda isn’t triggered
1. Check if GitHub WebHook is working correctly
1. for Prod account, need Apache Infra team access
2. for dev account, tested on my personal fork
1. https://github.com/ChaiBapchya/incubator-mxnet/settings/hooks/187804995
2. Check on CW Logs for any errors
1. Dev account : CW → Log Groups → /aws/lambda/mxnet-ci-bot-test-send
3. Jenkins Lambda isn’t triggered
4. Problem within Jenkins Lambda function
1. Check on CW Logs for any errors
1. Dev account : CW → Log Groups → /aws/lambda/mxnet-ci-bot-test-jenkins