You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the great work with the aws-sqs plugin!
We are trying to use multiple CodeCommit repos with a single SQS queue. Currently, when the plugin receives any sort of notification from CodeCommit, it triggers the build of ALL jobs that matches the branch (of the SNS message), but without consideration of the repo that generated it (eventSourceARN).
For example, if I have two repos ("FOO" and "BAR") and a job for each that tracks the "master" branch, a notification of "FOO/master" being updated will trigger both jobs, which is obviously not correct.
Is it possible to extend this plugin to use the eventSourceARN to filter out which repo to trigger? Without this we will have to create N SQS queues for N repos, which can be a lot, and also makes the Jenkins configuration of them very cumbersome.
For your reference here is a sample SNS message that shows where eventSourceARN is located.
Hi Nick,
Thank you for the great work with the aws-sqs plugin!
We are trying to use multiple CodeCommit repos with a single SQS queue. Currently, when the plugin receives any sort of notification from CodeCommit, it triggers the build of ALL jobs that matches the branch (of the SNS message), but without consideration of the repo that generated it (eventSourceARN).
For example, if I have two repos ("FOO" and "BAR") and a job for each that tracks the "master" branch, a notification of "FOO/master" being updated will trigger both jobs, which is obviously not correct.
Is it possible to extend this plugin to use the eventSourceARN to filter out which repo to trigger? Without this we will have to create N SQS queues for N repos, which can be a lot, and also makes the Jenkins configuration of them very cumbersome.
For your reference here is a sample SNS message that shows where eventSourceARN is located.
Thank you for your help!
The text was updated successfully, but these errors were encountered: