-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
jenkins:2.150.2-alpine docker image
blueocean:1.10.2
swarm:3.15
matrix-auth:2.3 job-dsl:1.71
github:1.29.2
prometheus:2.0.0
htmlpublisher:1.18
workflow-aggregator:2.5
junit:1.26.1
slack:2.4
timestamper:1.8.10
github-sqs-plugin:2.1
lockable-resources:2.4
saml:1.1.2
github-oauth:0.31
github-pr-coverage-status:2.0.0jenkins:2.150.2-alpine docker image blueocean:1.10.2 swarm:3.15 matrix-auth:2.3 job-dsl:1.71 github:1.29.2 prometheus:2.0.0 htmlpublisher:1.18 workflow-aggregator:2.5 junit:1.26.1 slack:2.4 timestamper:1.8.10 github-sqs-plugin:2.1 lockable-resources:2.4 saml:1.1.2 github-oauth:0.31 github-pr-coverage-status:2.0.0
after upgrading to blueocean to 1.10.2, the github-sqs-plugin:2.1 stopped pulling github messages off of the SQS queue. We use the github-sqs-plugin to receive github webhooks from behind our firewall. We also use an IAM role, so we don't hard code the AWS creds.
When I roll back to the previous docker image with blueocean:1.10.1, The github-sqs-plugin:2.1 receives messages from the SQS queue successfully.
Unfortunately I'm not seeing any exceptions in the Jenkins logs related to the sqs plugin, this issue seems to happen silently.
Right now we are stuck on blueocean 1.10.1 & I cannot upgrade our jenkins instance or plugins until this issue is resolved.
