The plugin currently:
To use this feature, first go to the global configuration and add a SQS Profile
To verify that you have correctly configured the SQS profile you can click "Test Access" this checks to see if the Queue exists in your SQS account and tries to create it if it does not. You can always manually create the queue via Amazon AWS Management Console
Once that configuration is done, go to the project config and simply check "Build when a message is published to an SQS Queue" under "Build Triggers".
You can choose to have Jenkins automatically manage the Github SQS hook automatically. You'll specify GitHub user names and passwords so that Jenkins can login as you to do this, and yes, we need your password and not API token because GitHub doesn't have an API for managing service hooks.
If you want to manually manage the service hook or inspect the config you navigate to the Admin -> Service Hooks section and select the SqsQueue hook and enter your AWS Access Key, the SQS Queue name and your AWS Secret key. The Queue name will need to match the Queue name you have configured in Jenkins
To use the GitHub SNS service hook to trigger builds you need to manually configure it. You need to navigate to the Admin -> Service Hooks section and select the AmazonSNS hook and enter Aws Key, Aws Secret, Sns Topic and Sqs Queue. The Sqs queue is used by the SNS service to create a subscription for that queue. The queue name will need to match the queue you have configured in your Jenkins SQS Profile config.
Skip to end of metadata Go to start of metadata